[
https://issues.jboss.org/browse/WFLY-2816?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-2816:
------------------------------------
Thanks, I wanted to better understand the use case. You shouldn't have to set
hibernate.transaction.manager_lookup_class on WildFly but assume you are on WebSphere.
[Open this link to see some
hints|https://docs.jboss.org/author/display/WFLY8/JPA+Reference+Guide#JPA...]
in the documentation.
Favour jboss-persistence.xml if present
---------------------------------------
Key: WFLY-2816
URL:
https://issues.jboss.org/browse/WFLY-2816
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JPA / Hibernate, Server
Reporter: Christopher Klein
Assignee: Scott Marlow
Priority: Minor
For developing for different target application servers (e.g. JBoss and WebSphere) it
would be nice if WildFly favours a jboss-persistence.xml instead of the original
persistence.xml.
The jboss-persistence.xml is specific for the deployment inside WildFly, the
persistence.xml would be the fallback/default for other application servers.
--
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