-
1. Re: Upgrade to Hibernate 4.3
smarlow Jan 15, 2014 11:46 AM (in response to thomasgo)Hi,
In theory, the Jipijapa integration code could be back ported to AS 7 but we have already moved on to building AS 8 (now called WildFly 8).
The reason why adding the Jipijapa integration jars to AS7 didn't work, is that you would also need other code changes that use the Jipijapa interfaces.
If you need a Hibernate bug fixed for your production use of AS 7, look into using JBoss EAP (product version of AS 7) which might have the Hibernate bug fixed already. Do you know a HHH jira number for the bug?
Scott
-
2. Re: Upgrade to Hibernate 4.3
ybxiang.china Jan 15, 2014 10:26 PM (in response to thomasgo)Hibernate 4.3.0 has a severe bug:
[HHH-8756] Exception on lock mode when setting lock mode NONE for named query - Hibernate JIRA
https://hibernate.atlassian.net/browse/HHH-8817
This bug is caused by this feature: [HHH-8563] javax.persistence.Query#getLockMode should throw ISE in some cases - Hibernate JIRA
-
3. Re: Upgrade to Hibernate 4.3
thomasgo Jan 16, 2014 7:03 AM (in response to smarlow)Yes, the bug we need to be fixed is [HHH-7539] Interceptor.afterTransactionCompletion not called when transaction completes via JTA sync - Hibernate JIRA