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

[Hendy Irawan (JIRA)]

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

Hendy Irawan commented on AS7-3110:
-----------------------------------

BTW.. can someone confirm if this is a bug in JBoss JPA Container or Spring Data JPA ..?

Here's the relevant part of code in Spring Data JPA 1.1.0.RELEASE:

{code}
public class JpaRepositoryFactoryBean<T extends Repository<S, ID>, S, ID extends Serializable> extends
		TransactionalRepositoryFactoryBeanSupport<T, S, ID> {

	private EntityManager entityManager;

	/**
	 * The {@link EntityManager} to be used.
	 * 
	 * @param entityManager the entityManager to set
	 */
	@PersistenceContext
	public void setEntityManager(EntityManager entityManager) {

		this.entityManager = entityManager;
	}
...
{code}

Note that JpaRepositoryFactoryBean is not annotated with @Stateless or any EJB annotations, in fact it's a plain class. Why is it scanned ?
                
> Enhance validation message when multiple persistence units are found
> --------------------------------------------------------------------
>
>                 Key: AS7-3110
>                 URL: https://issues.jboss.org/browse/AS7-3110
>             Project: Application Server 7
>          Issue Type: Enhancement
>          Components: JPA / Hibernate
>            Reporter: Markus Dahm
>            Assignee: Scott Marlow
>            Priority: Minor
>             Fix For: 7.2.0.Alpha1
>
>
> 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira