Jakarta Data 1.1

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

• Ability to define query restrictions dynamically (#829)
• Bring parameter based automatic query methods up to the level of what Query by Method Name can do for static queries (#857)
• Consider additional annotations related to Jakarta Persistence (#470)
• Query Fragments (#546)
• Multiple item select lists/DTOs/Entity Views (#539)
• Life cycle events (#373)
• Reactive patterns (#17) and integration with Jakarta Concurrency Asynchronous (#19)
• Move Jakarta Data Query Language to Jakarta Query specification (if accepted and included in Jakarta EE 12) where it will remain fully compatible.
• Configuration via Jakarta Config (if Jakarta Config is released and makes it into Jakarta EE 12 in time)
• Explicitly state where NoSQL databases can raise errors for function the database type is not capable of (#782)
• TCK refactoring and enhancements to more logically split out tests that are targeted at various levels of database support (key-value, column, document, graph, relational).

For a detailed list of issues see: https://github.com/jakartaee/data/milestone/4