[
https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin....
]
Luca Masini commented on FORGE-621:
-----------------------------------
Until WebLogic 10.3.4 the provider was OpenJPA, starting from 12c it's EclipseLink.
Thank from the point of view of the container.
Looking at Hibernate, when we inject it into the PU it should detect that is running under
WebLogic and use the correct Transaction Manager, but someway WLS is not detected (I
looked at sources, the code for WLS detection is there !!) and we need to specify it as a
property.
I agree that having another container listed is a good option, so I'll commit here as
soon as I understand how to do that.
Ciao.
Need to configure "hibernate.transaction.jta.platform" when
using Hibernate outside of JBoss AS
-----------------------------------------------------------------------------------------------
Key: FORGE-621
URL:
https://issues.jboss.org/browse/FORGE-621
Project: Forge
Issue Type: Bug
Components: Java EE APIs
Affects Versions: 1.0.6.Final
Reporter: Luca Masini
Labels: hibernate_persistance_layer, weblogic
Fix For: 1.1.3.Final
Attachments: JPAContainer.java, WebLogic12cContainer.java
When running in an App Server that is not JBoss we need to configure the
"hibernate.transaction.jta.platform" to bind the JTA resource to the current
EntityManager. For instance, using WebLogic 12c:
<property name="hibernate.transaction.jta.platform"
value="org.hibernate.service.jta.platform.internal.WeblogicJtaPlatform" />
I think that a new parameter is needed on the persistence setup command.
--
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:
http://www.atlassian.com/software/jira