I am trying out RC3 due to the new scoped classloading for EARs functionality... Still, I am having trouble so I'm not sure I understand how it is supposed to work...
I have 2 EARs. One is the "standard" EAR, the other the "modified" EAR. The "modified" EAR has a jboss-app.xml file that contains: <jboss-app> <loader-repository>com.myrecords:loader=myrecords.ear</loader-repository> </jboss-app> The "standard" EAR gets deployed first and it is very happy. The "modified" EAR reports errors during deployment... These errors are because the container claims that one of my EJBs doesn't have the abstract accessors required for CMP for one of the fields that only exists in the modified version. It seems like the container is taking the ejb-jar.xml file from the "modified" EAR and comparing it against the bean class from the "standard" EAR, which obviously doesn't match. It was my understanding that with the scoped classloaders it would look in its containing package before it would look elsewhere. Is this not correct? Have I done something wrong? Any help is greatly appreciated. Thanks, Hunter _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
