Create Domain Specific Language API generator for hand coded FinderImpls

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.2.10 DXP FP17, 7.2.10.6 DXP SP6, Master
• Component/s: Core Infrastructure
• Labels:
  • 7.3-ce-ga2
  • 7010-sp-pending
  • 7110-sp-pending
  • 7210-sp-pending
  • fc_20_06
  • liferay-dxp-72-sp6
  • liferay-fixpack-dxp-17-7210
• Branch Version/s:
  7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Epic/Theme:
  • Core-Infra-Improvements
• Git Pull Request: https://github.com/shuyangzhou/liferay-portal/pull/8866

Domain Specific Language API generator for hand coded finder implementations.

Main goals of new API

1. Disallow syntax errors and using database specific clauses
2. Create compile time safety checking for table references between modules
3. Merge locations of SQL with usage to reduce mistakes in finder implementations
4. Merge SQL generation API with parameter binding API to ensure type safety and correct query parameter binding
5. Easier lookups for DB table sync when using Hibernate
6. Add potential for caching multi-table queries
7. Add potential for safer SQL based APIs

Notes

1. The SPI does not need to be referenced by DSL users unless they are integrating the DSL usage with a DB or rewriting queries dynamically
2. All classes in the SPI are immutable to preserve easier debugging of queries and much of the "feel" from string queries
3. Aliasing is fully supported but can be a challenge to use correctly because of immutability
4. Database translation for functions is performed by code in kernel

Example Usages

• LayoutFinderImpl
• AssetTagFinderImpl