You would need to bind your session beans under different jndi names
/docs/tutorial/stateful_deployment_descriptor/stateful.html in the distribition contains an example of overriding the jndi name in your.ejb3/META-INF/jboss.xml
If you plan on deploying several versions of the same beans you would need to scope your deployments
How do I scope a deployment?
Now deployment of two stateless session beans with different JNDI names in META-INF/jboss.xml causes the following exception:
javax.management.InstanceAlreadyExistsException: jboss.j2ee:service=EJB3,name=my.pkg.StatelessSampleBean already registered.
Using JNDIView MBean I found that a bean is deployed using both the interface name and the name defined in META-INF/jboss.xml.
thi s is a bug as the EJB container's kernel name should be determined from the EAR and JAR it is deployed in. I'll log a bug in JIRA on this. Apologies.
Ok. Will this issue be fixed in AS 4.0.3 SP2? If yes, what is the planned release schedule? Or can I somehow install a fixed version of EJB 3.0 container before that?
BTW, what is the easiest workaround? Changing bean's interface name causes changes also into web tier.