Bug 710509
Summary: | upgrade hibernate | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | John Mazzitelli <mazz> |
Component: | Core Server | Assignee: | Nobody <nobody> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 4.0.1 | CC: | hrupp, jshaughn |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Mazzitelli
2011-06-03 15:13:43 UTC
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. 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. |