User development, A new message was posted in the thread "Persistence unit issues when migrating to JBOSS 5.1.0": http://community.jboss.org/message/520301#520301 Author : Dragos Bobes Profile : http://community.jboss.org/people/dbobes Message: -------------------------------------------------------------- Hi Jaikiran, I appreciate the time you spent on this issues.   This is how I had the ear in the first place and it didn't work. If you look at my first post on this discussion the persistence.xml file was located in the META-INF folder of the myseammodule.jar which was located in the root of the ear (also this jar was specified as an ejb module in application.xml). In this case extejbmodule.jar didn't have access to the persistence unit.   I still have to try this option but right now I encountered another scoping problem. The extejbmodule.jar (from my first post) has a stateless bean defined like this:   @Stateless(name="Server", mappedName="myapp/Server/local")   In the seam's components.xml file I have defined the server component like this:       <component name="server" auto-create="true"               scope="event" jndi-name="myapp/Server/local"               class="com.company.ServerImpl"> But when I try to inject the component into a seam bean:   @In Server server;   it throws:   javax.naming.NameNotFoundException: Server not bound   In debug, it fails when it tries to lookup the "myapp/Server/local" jndi name. This was not a problem in JBOSS 4.2.3 so it must be also related to the new scoping where entities from one module are not visible to the others.   Any ideas? -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/520301#520301