A couple of thoughts... Are you sure that you do not have a copy of your shared classes still packaged somewhere in your .war? Have a look at use-case #4 here
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases in regards to the HierarchialLoaderRepository class loader's precedence over the parent. The class is not loaded into the repositorie's cache until it is requested, and if it is deployed somewhere in your .war, and your .war is the first thing to request that class, the scoped version of that class will be returned. So both of your .war's will have their own versions of the class, cached in their own repositories, which will be siblings of each other, which will cause the ClassCastException. As an aside, are there other classes that you want to be isolated between these two .war's? It may be a silly question, but it's a little funny for me to see java2ClassLoadingCompliance set to true, then have a loader-repository configured as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922347#3922347 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922347 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
