Hi Renier
Thanks for your post. An update on the situation is as follows:
JBoss3.2.6's {tomcat}/META-INF/jboss-service.xml file must be changed
to -
<attribute name="Java2ClassLoadingCompliance">false</attribute>
<attribute name="UseJBossWebLoader">false</attribute>
JBoss4.0.2 comes from it's mother like above - I reckon someone figured
out that the default in 3.2.6 was a bad idea.
With these parms set to false the applications mentioned in my previous
post work as expected, referencing their own versions of the class in
question.
My next test will be to create two EAR deployments containing EJB's
which use particular versions of JAR files (packaged within the
respective EAR). I then need to make sure that the EJB's reference the
correct version of the EAR'ed JAR.
I will keep you posted.
Thanks again for the tip.
Paul
