[
https://issues.jboss.org/browse/FORGE-621?page=com.atlassian.jira.plugin....
]
Luca Masini commented on FORGE-621:
-----------------------------------
Sorry George, I feel I really need a "Git for dummies" book :)
Anyway I looked at Hibernate code and I think there is something there that is not working
as expected. Reading JPA 2.0 specs seems like that Hibernate should do that automatically
(something it does with JBoss).
I would like to have your opinion, should we fix that in Forge in the meanwhile ??
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