[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3579) AS5 deploys PUs from /WEB-INF/classes/META-INF/persistence.xml

[ https://jira.jboss.org/jira/browse/JBSEAM-3579?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-3579: ----------------------------------- The problem was present in any examples that deployed as a WAR archive and used JPA. It turns out the hibernate example was not a problem. JBoss AS 5 is going to load any persistence units it finds in the classpath. Thus, we don't need to have Seam load the persistence unit. It's possible to add the jboss.entity.manager.factory.jndi.name property to the JPA configuration so that the EntityManagerFactory binds when the application deploys to JBoss AS 5. Then, in compoennts.xml, we use an Ant replacement token to toggle the installation of the <persistence:entity-manager-factory> compoent. If that component is absent, Seam will look to JNDI. This is controlled through the loadPersistenceUnits token. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira