[jboss-jira] [JBoss JIRA] (WFLY-1032) Enhance validation message when multiple persistence units are found

[Oliver Gierke (JIRA)]

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

Oliver Gierke commented on WFLY-1032:
-------------------------------------

I've just been [pointed to|https://twitter.com/g_scheibel/status/347264619607363585] the fact that only jars with a {{META-INF/beans.xml}} should actually be scanned in the first place (see section 12.1. of the CDI spec). So it might make sense to simply exclude JARs that don't have that from the checks? If that works for you could even stick to the strong rejection as it seems to make sense in case someone is really doing some misconfiguration in ones CDI beans.
                
> Enhance validation message when multiple persistence units are found
> --------------------------------------------------------------------
>
>                 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