Bug 710509 - upgrade hibernate
upgrade hibernate
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
Unspecified Unspecified
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2011-06-03 11:13 EDT by John Mazzitelli
Modified: 2011-07-25 17:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Mazzitelli 2011-06-03 11:13:43 EDT
Now that we have a bit more breathing space before next release, I would like to ask upgrade our Hibernate library now.

Right now, we are using a relatively old Hibernate version - and an unreleased, custom patched one at that (3.2+)

If we upgrade Hibernate now, it would give us a good amount of time from now to release to see if we hit any issues.

Bryan K did this before which never made it into master. He emailed a patch to rhq-devel back in Jan 2010. Here's the thread:


Note, in the last message in the thread, he attached an updated revision 
of the patch.
Comment 1 Charles Crouch 2011-07-25 14:20:08 EDT
Dropping priority. Jay did some investigation here and iirc concluded it wasn't worth the effort right now. Jay please add links/details

I think we'll probably be better off waiting until JBAS7.1/EAP6 is out and using the version which ships with that.
Comment 2 Jay Shaughnessy 2011-07-25 17:27:12 EDT
I could have sworn I had updated this already but...

I had done some initial work on this upgrade and decided it was not worth the effort.  The main issue is that a significant upgrade to Hibernate requires JPA2 support and that does not come with AS4.2.3, our current container.  We could potentially have force-fitted it into place but I was not encouraged by posts I had seen on the web about others trying to do something similar.

We could try updating to the last version prior to the required JPA2 support, but again, it didn't seem like a big win.

So, a newer version of Hibernate should go hand in hand with our next container version upgrade, probably a leap to a thinned AS7+ at some point.

Note You need to log in before you can comment on or make changes to this bug.