Jakarta Data 1.0

The following are planned for the 1.0 release of Jakarta Data:

• Define the repository pattern, leaning heavily on what existing implementations have already done.
• Define ways of performing sorting and pagination for repositories.
• Define the entity model, reusing from Jakarta Persistence and Jakarta NoSQL.
• Align the API with Java Records style.
• Enable providers of Jakarta Data to be plugged into Jakarta EE products.
• Allow providers to preserve their vendor-specific dependency injection models, while also enabling Jakarta EE products to support dependency injection of Jakarta Data repositories via Jakarta CDI.
• Define interactions with other Jakarta EE specifications (such as Persistence, Transactions, CDI, and NoSQL) when they are available.
• Write a TCK with different modes for standalone providers and Jakarta EE product providers, so that the former can certify as providers independently of Jakarta EE profile-specific function and the latter can certify as providing Jakarta EE profile-specific function. The TCK might also have modes for covering the different entity models used (those from Jakarta NoSQL vs Jakarta Persistence).