[
https://issues.jboss.org/browse/WFLY-1032?page=com.atlassian.jira.plugin....
]
Oliver Gierke commented on WFLY-1032:
-------------------------------------
So why is the class then scanned at all? {{@PersistenceContext}} injection is only
supposed to happen for managed classes (according to 7.2.1 of JPA 2.0) which the one under
consideration clearly is not (it's neither JavaEE bean nor fulfils the requirements to
be considered a CDI bean).
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