[jboss-jira] [JBoss JIRA] (WFLY-2816) Favour jboss-persistence.xml if present

[Christopher Klein (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12939086#comment-12939086 ] 

Christopher Klein commented on WFLY-2816:
-----------------------------------------

As you already guessed it, yes it is about developing on WildFly and deploying in production to WebSphere.

The <non-jta-data-source> content and some properties (<properties><property name="<property name="hibernate.transaction.manager_lookup_class" value="..." /></properties>) differs between both environments. Creating two more or less same EAR artifacts with different persistence.xml content seems to be a little bit messy and I am trying to avoid it.

The hints you mentioned: Can you please give me an example or a link? I looked upon the WildFly documentation but I didn't get it.

                
> 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