first a little bit of background information: We habe multiple applications (Java Swing Clients) that share about 20 EJB 2.x modules. Until now these EJB modules were deployed to a JBoss AS 4.2.3 GA directly, i.e. withouth an EAR file. This shall be changed now to allow the applications to use different versions and so be deployed separately. For this the beans shall be packaged in application-specific EAR files. That means that at least some EJB 2.x Modules are deployed multiple times in multiple EARs. Since I am experienced with EJB 3.0 I thought this would be no kind of a problem, because JBoss appends the EAR name as JNDI-Prefix here. Now I had to learn that the JBoss AS behaves differently for EJB 2.x modules by default and so I am experiencing JNDI name conflicts.
So my question is: Is is possible to configure the JBoss AS in version 4.2.3 GA to add the EAR JNDI prefix (or EAR scope) when deploying EJB 2.x beans?