I have a WAR file with an applet. The applet requires some old classes that conflict with those required by JSPs/Servlets in the WAR file. The classes for the applet are in a jar file, applet_only_classes.jar. When I deploy my WAR, JBoss creates a UCL for this jar file, even though it is only intended to be 'served', not used by the server. Every now and then I get ClassFormatErrors and Linkage problems inside JBoss because when the server code goes looking for classes, it finds these old classes instead of the correct ones.
WAR: - applet_only_classes.jar - *.html - *.jsp - WEB-INF/web.xml - WEB-INF/lib/server_classes.jar Shouldn't only stuff in WEB-INF be subject to sub-deployment? That would solve my problem because applet_only_classes.jar would not be found and therefore would hose up the server. Basic problem is, SubDeployerSupport.init() tries to deploy everything in a 'deployable item' through SubDeployerSupport.processNestedDeployments(). What happens if you want to have a web site that serves up your old application releases as jar files? We could override isDeployable in AbstractWebContainer and do a super.isDeployable() && 'WEB-INF' is in the given url. Is there someway around this that I'm missing? Thanks, Michael ------------------------------------------------------- This SF.NET email is sponsored by: Take your first step towards giving your online business a competitive advantage. Test-drive a Thawte SSL certificate - our easy online guide will show you how. Click here to get started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
