[ https://issues.jboss.org/browse/JBSEAM-4975?page=com.atlassian.jira.plugi... ] Tomas Remes updated JBSEAM-4975: -------------------------------- Description: When you generate Seam project in Seam-gen, it will create build.xml inside your new project. In this build.xml file there is handled "puJndiName" variable, which is then referenced in components.xml. The problem is that this variable is not set properly, because it depends on value of variable "seamBootstrapsPu" and this variable is assigned based on availability of ${jboss.home}/lib/jboss-vfs.jar file, which does not exist in AS7. So the problem is this line (69) in build.xml: <available file="${jboss.home}/lib/jboss-vfs.jar"/> When the entityManager could'nt be found, following exception occurs: {noformat} Caused by: javax.naming.NameNotFoundException: entityManager -- service jboss.naming.context.java.entityManager at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:119) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:257) {noformat} was: When you generate Seam project in Seam-gen, it will create build.xml inside your new project. In this build.xml file there is handled "puJndiName" variable, which is then referenced in components.xml. The problem is that this variable is not set properly, because it depends on value of variable "seamBootstrapsPu" and this variable is assigned based on availability of ${jboss.home}/lib/jboss-vfs.jar file, which does not exist in AS7. So the problem is this line (69) in build.xml: {noformat} <available file="${jboss.home}/lib/jboss-vfs.jar"/> {noformat} When the entityManager could'nt be found, following exception occurs: {noformat} Caused by: javax.naming.NameNotFoundException: entityManager -- service jboss.naming.context.java.entityManager at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:119) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:257) {noformat} -- 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

[ https://issues.jboss.org/browse/JBSEAM-4975?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-4975: --------------------------------------- set to java:/$project.nameEntityFactoryName and not rely on jboss-vfs.jar anymore -- 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

[ https://issues.jboss.org/browse/JBSEAM-4975?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-4975. --------------------------------- I am closing the issue. All issues has to be filed against 2.3.0.Final from now. -- 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