EJB versioning

[david.wade]

Have a problem trying to use different versions of an EJB.

Have successfully deployed two EAR files, manager-v1.ear and manager-v2.ear, each containing an EJB Jar with an EJB named "Manager" with the same named remote and home interfaces. The two EJBs bind to JNDI under the names ejb/ManagerV1 and ejb/ManagerV2. The separate EAR and versioned EJB's are clearly visible in the web-console.

However when I try to access a particular version of the EJB, using the versioned JNDI name from a standalone program, I always get ManagerV1.

Is there anyway of getting this versioning to work without having to have version numbers incorporated into the bean name itself (or seperate servers)?

David

[starksm64]

JBoss has a flat default class loading model described here:
http://sourceforge.net/docman/display_doc.php?docid=14516&group_id=22866

If you are deploying multiple versions of the same classes in an ear, you need to isolate the classes using an ear/META-INF/jboss-app.xml descriptor with a unique JMX object name as the loader-repository
value.

<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE jboss-app
 PUBLIC "-//JBoss//DTD J2EE Application 1.3V2//EN"
 "http://www.jboss.org/j2ee/dtd/jboss-app_3_2.dtd">

<jboss-app>
 <loader-repository>mydomain:loader=appv1.ear</loader-repository>
</jboss-app>

[david.wade]

That worked.

thanks.