EJB conflicts during deployment

[vinodkv]

Hi,

We are porting applications from WAS4 to JBoss 4.3.

We are facing issues when we deploy the EARs on the Server. We are using the default profile of JBoss.

We have 2 applications Order and OrderManagement.
These applications have the following common EJBs with the exact same code
- AvlEjb
- AIMEJB
- AvlHandleEjb

Can you give us a strategy where these EJBs do not conflict with each other when we deploy both the Application EARs.
Can the EJBs be isolated from each other ?

When we deploy an EAR, does it create a boundary within which all the JARs and EJBs are running.
If this is the scenario, the deployment of the same EJBs from a different application would not affect each other as they are running within different EAR boundaries.

Thank you in advance

[vinodkv]

All the EJBs used in the application are of Version 1.1

[wdfink]

To isolate the classloading you have to configure it.

See http://community.jboss.org/wiki/ClassLoadingConfiguration for this.

Also you have to separate the JNDI names of the EJB's, but I think you have done this via deployment descriptor, right?

If it is correct configured a redeploy of one app has no affect to the other.

Helpful links for classloading are also:

http://community.jboss.org/wiki/ClassLoadingOverview

http://community.jboss.org/wiki/JBossClassLoadingUseCases