camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5849) Upgrade camel-hibernate to Hibernate 4.1.x
Date Fri, 21 Dec 2012 08:09:13 GMT


Claus Ibsen commented on CAMEL-5849:

People can pick and chose which Spring version they want to use. So they can use Camel 2.10
with Spring 3.1. etc. And there is some components that would require Spring 3.1+ moving forward.

We should IMHO consider dropping support for Spring 3.0 as that branch is dead. SpringSource
does NOT support that anymore.

Fell free to work on this camel-hibernate component to require Hibernate 4 + Spring 3.1. Thats

And also fell free to use the Hibernate API directly. If ppl want to use JPA there is camel-jpa.
Then you can use the extra stuff that Hibernate has, which is not in JPA etc.
> Upgrade camel-hibernate to Hibernate 4.1.x
> ------------------------------------------
>                 Key: CAMEL-5849
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: extra
>            Reporter: Brett E. Meyer
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.11.0
>         Attachments: CAMEL-5849.patch
> Unless Hibernate 3.6.x is used for a specific reason, it'd be great to upgrade camel-hibernate
to 4.1.x.  I already have this finished in my workspace (minor code changes w/ it) and would
be willing to provide the patch.
> Is Spring compatibility the concern?  Technically they support Hibernate 4 as well.
> I'm also willing to maintain this component long term if there's interest.  I'm one of
the Hibernate core developers ( and use camel-hibernate in a few
side projects.  I know most users typically use camel-jpa, but there are Hibernate-specific
features that could certainly be rolled into camel-hibernate if it would be used.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message