[jboss-jira] [JBoss JIRA] (WFLY-1032) Improve how we handle when multiple persistence units are found and no unitName is specified

[Scott Marlow (JIRA)]

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

Scott Marlow commented on WFLY-1032:
------------------------------------

Oliver, this jira is not about improving how the [JPAAnnotationProcessor|https://github.com/wildfly/wildfly/blob/master/jpa/core/src/main/java/org/jboss/as/jpa/processor/JPAAnnotationProcessor.java] scanning for JPA annotations.  

I'm open to discussion and improvements to WildFly 8 code, to work better with Spring.  I would rather not use this jira.

Is this the only issue that you want to discuss about improving WildFly/Spring integration?  Or will there be other issues also to discuss?  We can probably create a discussion thread on [Snowdrop|https://community.jboss.org/en/snowdrop?view=discussions] and cross post the link here.
                
> Improve how we handle when multiple persistence units are found and no unitName is specified
> --------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1032
>                 URL: https://issues.jboss.org/browse/WFLY-1032
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: JPA / Hibernate
>            Reporter: Markus Dahm
>            Assignee: Scott Marlow
>            Priority: Minor
>             Fix For: 8.0.0.Alpha2
>
>
> The current message is
>     Caused by: java.lang.IllegalArgumentException: JBAS011470: Persistence unitName was not specified and there are 9 persistence unit definitions in application deployment "test.ear".  Either change the application to have only one persistence unit definition or specify the unitName for each reference to a persistence unit.
> Yet what is always helpful in search of such validation errors is the context.
> In that case the offending class name would suffice, you should have this information at hands since you're scanning the classes, right?
>  
> Given that information I'd have found the problem immediately.

--
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