How to deploy same ejbs twice in the same server

[Farouk Sherefudheen]

Hello All
I have a situation where in I have a common ejb code to be deployed as a part of two applications.

IBM Websphere version 4 is the one which i am using where in there is only
one JNDI name for the ejb.

App1 will use web xml reference using ejb/EJB1
App1 code will look up using java:comp/env/ejb/EJB1
Deployment In server maps ejb/EJB1 to ejb/XYZ/com.package.homeInterfaceName

No reference in web xml
App code will look up using com.package.homeInterfaceName (Default Name for ejb). So no explicit reference need during deployment as the client will be
able to find out EJB using default Name in the JNDI name space

Please Help this is quite urgent

[Roshan Lal]

I deployed two beans with same implementation code in websphere 5.1.
When creating beans, you give them different bean names, different jndi names and same classes for home, component, bean classes etc. That's all was required. The client gets to them via jndi names which are different
so there has not been a problem at all for me.

IBM Websphere version 4 is the one which i am using where in there is only
one JNDI name for the ejb.

I have not worked with Websphere 4.0 so I may be missing something. But this
"one JNDI name for the ejb" is not clear to me. There will be TWO ejbs deployed, albeit sharing same code, so they can have two different jndi names.

Hope it helps
Roshan

[Farouk Sherefudheen]

Hello Roshan
Thanks for your help
In websphere 4.1 there is no concept of local jndi namespace, which is available to Websphere 5.
Now this code is a maintanined by us and is a part of generated webservice JCA code by WSAD IE.

Now the problem is we just give other team this code and they do no touch it and use it as a part of their application.

So we in our client we refer to it using a alias name pointing to a jndi name which is mapped during deployment to the EJB

But other team is using the default reference in the wsdl ejb client file the home interface and which would be added to the server jndi name space when the ejb is again deployed.

Do I make any sense?