In trying to deploy multiple ears that uses shared ejb-jars in the same instance of JBoss, I'm using scoped deployment of ears and modifying the global JNDI name of the session beans:
app1.ear (scoped)
shared-ejb.jar (JNDI name ejb/Foo -> ejb/Foo/app1)
non-shared-ejb.jar, etc.


    app2.ear (scoped)
        shared-ejb.jar (JNDI name ejb/Foo -> ejb/Foo/app2)
        non-shared-ejb.jar, etc.

I encountered a problem with MDBs. I have an MDB in shared-ejb.jar. There is no JNDI name for me to alter because it is an MDB. However the deployer assigns a local JNDI name to it anyway based on its ejb-name. My MDB named ejb/Bar occupies the JNDI name /local/ejb/Bar upon deployment. And this causes a conflict between app1.ear and app2.ear when deployed in the same instance of JBoss.

The only way out that I can see is to change the ejb-name of the MDB. Are there other alternatives?

Thanks for your help.

--
Weiqi Gao
[EMAIL PROTECTED]




-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to