[Issue_608] [Preview] Jakarta Data support in standard WildFly #666
Conversation
bstansberry
force-pushed
the
Issue_608
branch
from
1ee21de to
58ed7f3
Compare
github-actions
bot
added
stability-level/preview
| I'm an application developer and I'd like to be less concerned with the mechanics of manipulating persistent data. I'd like to define my entities and then write an interface that describes the CRUD and data access operations I need. I code against that interface and let WildFly take care of generating the interface implementation that deals with the DB. | ||
|
|
||
| I'm an application developer and am familiar with the Repository pattern from use of Spring Data. I'd like to use that pattern in WildFly in non-Spring applications. | ||
|
|
||
| I'm an application developer who's used Deltaspike Data, which uses a repository pattern. But it doesn't support EE > 8, so I'm looking for a similar technology to run on the latest WildFly releases. |
There was a problem hiding this comment.
You might want to mention that users need to be fine with having less flexibility, in particular:
- Simpler query language.
- No lazy loading -- or only explicit lazy loading by using Hibernate ORM native APIs.
- More limited support for dynamic queries; I think there is some support for dynamic predicates, but it far from the Criteria API.
- And so on.
Which is fine, but it does mean that it's not just about what developers "like", it's also about the complexity of their use case: Jakarta Data is great in many cases, but may be too limited in others.
Note that it's perfectly possible to use standard JPA, native Hibernate ORM APIs, and Jakarta Data in the same application. Depending on how the stateless session is injected into Jakarta Data, it's probably even possible to use Hibernate ORM APIs (StatelessSession) and Jakarta Data in the same transaction.
There was a problem hiding this comment.
Thanks @yrodiere. I incorporated a lot of your info above in the first user story.
bstansberry
force-pushed
the
Issue_608
branch
from
58ed7f3 to
e917b0c
Compare
github-actions
bot
added
stability-level/preview
| ** This layer will be shared with the `wildfly-preview` feature pack. (This is the norm for `wildfly-ee` layers). | ||
| * The Jakarta Data API artifact *must not* be part of the standard WildFly user boms. We limit the user boms to `community` stability artifacts. | ||
| * The Jakarta Data API artifact must contintue to be part of the WildFly Preview user boms. | ||
| * The wildfly-tck-runners Jakarta Data runner will be modified to test the `wildfly` feature pack by default, while allowing testing of `wildfly-preview`. |
There was a problem hiding this comment.
Note: I'll do this after the 35 Beta release as the runner shouldn't depend on a SNAPSHOT.
|
Thanks @yrodiere and @jasondlee |
For #608