[jboss-jira] [JBoss JIRA] (WFLY-9132) Applications won't deploy if their persistence.xml have multiple persistence units

[Scott Marlow (JIRA)]

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

Scott Marlow commented on WFLY-9132:
------------------------------------

We did make a change that likely is causing the deployment error that your seeing.  Please let us know the deployment error message (include the entire exception stack trace also).

[https://docs.jboss.org/author/display/WFLY10/JPA+Reference+Guide#JPAReferenceGuide-Persistenceunitproperties] mentions the "wildfly.jpa.default-unit" persistence unit property, which you could set to true, in the persistence unit that you want to be the default (out of the multiple persistence units that you have in your application).  Hope that helps.

Scott

> Applications won't deploy if their persistence.xml have multiple persistence units
> ----------------------------------------------------------------------------------
>
>                 Key: WFLY-9132
>                 URL: https://issues.jboss.org/browse/WFLY-9132
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 10.1.0.Final
>         Environment: Windows 10 64 bit
> Wildfly 10.1.0
>            Reporter: Bobby Bassman
>            Assignee: Scott Marlow
>
> Applications won't deploy if their persistence.xml have multiple persistence units. This was not a problem with EAP. Now, Wildfly requires that each @PersistenceContext have a 'unitName' parameter. WIth EAP 6.4, if a @PersistenceContext did not have a 'unitName' parameter, then the default PU was used. By requiring that @PersistenceUnit have 'unitName', developers are forced to unnecessarily bind Java code to configuration.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)