OK, you should have clarified that earlier.
It's not java:comp/env that's conflicting here; it's the actual JNDI
name of the EJB which is same across two ear files. You need to
explicitly set it differently in different application, because
appservers are free to come up with any default name. You can use
sun-ejb-jar.xml to specify it. That way, your application code remains
same, only the deployment descriptor differs.
Thanks,
Sahoo
glassfish_at_javadesktop.org wrote:
> Well, say i put the same EJB into two different Enterprise Apps, or deploy the same enterprise appliction on the same server (again with different names). The EJB module has a session bean called: ClientBusinessFacade.
>
> I would look that up by using: java:comp/env/ClientBusinessFacade
>
> So I've noticed that even though there are two EAR's on the server, we end up with a conflict on the name of the EJB module in the two enterprise apps...
>
> Basically the whole objective is to have a different version of the enterprise application deployed on the same application server for each different client... It is possible a few of them will be running different revisions of that application.
> [Message sent by forum member 'the_thunderbird' (the_thunderbird)]
>
> http://forums.java.net/jive/thread.jspa?messageID=271742
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>