I'm a bit late on this thread ... as far as I can tell Tomcat doesn't look at the META-INF stuff at all. manifest classpaths have worked in tomcat because jboss put them into the parent classloader first. Is that something we should press Tomcat to fix, ie is reading the MANIFEST part of the .war deployer contract? (I think it ought to be)
I assume (and I can't instantly see where the deployer went to!) that you are still parsing out and adding classes from .ear MANIFEST classpaths and setting that classloader as the parent before sending the .war to the wardeployer. If that's the case, it would of course be possible for deployers to make .ear's not .war's and set the manifest classpath in there. Roland _________________________________________________________ View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=9260 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
