Yes, note that the new defaulting rules are that if you don't specify persistenceUnitJndiName, the JNDI name of the EMF would default to "java:/napEntityManager", in your case.
What I want to do for the next EJB3 release is sit down with Bill and define some defaulting rules for how resources and EMFs will be bound to the ENC or global JNDI *by default*, so that we can provide a similar functionality to org.jboss.seam.core.init.jndiPattern for resources and EMFs. That way we will eliminate the shitty mucking-with-JNDI-names stuff. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919081#3919081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919081 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
