[
https://issues.apache.org/jira/browse/CAMEL-21873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123069#comment-18123069
]
Claus Ibsen commented on CAMEL-21873:
-------------------------------------
Follow-up on the target version: camel-hibernate should target *Hibernate 8.x*,
not Hibernate 7.
* Hibernate 8.0 is not final yet (8.0.0.Beta3 is the latest on Maven Central).
It is built on Jakarta Persistence 4.0 and still runs on Java 17.
* Because of that, the component should use the native Hibernate API and *not
depend on camel-jpa*. camel-jpa stays on Hibernate 7 / Jakarta Persistence 3.2
for now, and the two cannot share one classpath.
* The longer-term plan is a platform jump in Q1 2027: Quarkus 4, dropping Java
17, and Hibernate 8 if it is GA by then. The component can be developed against
the 8.0 betas meanwhile (e.g. as a draft PR), and merged once Hibernate 8.0 is
GA and the platform upgrade lands.
* Please check the feature list in my previous comment against the 8.0 API
(StatelessSession, SKIP_LOCKED, SelectionQuery/MutationQuery, streaming), since
a major version may have changed some of these.
_Claude Code on behalf of davsclaus_
> camel-hibernate component
> -------------------------
>
> Key: CAMEL-21873
> URL: https://issues.apache.org/jira/browse/CAMEL-21873
> Project: Camel
> Issue Type: New Feature
> Reporter: Claus Ibsen
> Assignee: Ramu
> Priority: Major
> Fix For: 4.x
>
>
> Hibernate 7.x is going to be ASL2 licensed so we can have a first class
> component at Camel. It can use JPA/Hibernate APIs. But extending camel-jpa
> and using some of the extra powers of hibernate we can make this a bit easier
> for users than before with JPA and setting it up for Hibernate
> [https://in.relation.to/2025/03/14/orm-asl/]
>
> There was also the old camel-hibernate code at camel-extra we can take a look
> at
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
