[
https://issues.jboss.org/browse/AS7-2275?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2275:
-----------------------------------
It may take us a while to come to changing a future JPA specification. I do hope to hear
more feedback from others about how the ambiguous injection case should be handled (in a
portable fashion so applications work the same everywhere).
I am keeping the TRACE logging enhancements and the current ambiguous inject handling,
with one change to let application developers add a "default-unit" hint to the
persistence unit that should be injected.
I'll update the error message to suggest that the "default-unit" hint be
added to the correct persistence unit to inject.
Feedback?
Deployment error should result when ambiguous injection is specified
--------------------------------------------------------------------
Key: AS7-2275
URL:
https://issues.jboss.org/browse/AS7-2275
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Reporter: Stuart Douglas
Assignee: Scott Marlow
Fix For: 7.1.0.Beta1
If no name is specified PersistenceUnitSearch.resolvePersistenceUnitSupplier will return
a PU at random, rather than throwing an exception if more than one PU is found.
--
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