Scott, Jetty and Tomcat both use Jasper as their JSP engine.
Jasper expects it's classpath (for on-the-fly compilation of JSPs) as a list of files/dirs, but Jetty only gets a ClassLoader from JBoss. My integration code, walks up the CL tree, calling getURLs when possible, to put together a classpath to hand off to Jasper. That's the background - now the problem. When I run the jakarta-watchdog tests (large group of web-container tests ~400) in JBoss/Jetty, I end up with a huge classpath, which looks like it contains every jar ever loaded by JBoss. All the JSPs compile OK and we pass the testsuite. When I run the JBoss web test suite, the ClassLoader passed to Jetty only admits to knowing about the contents of the webapp being deployed, tools.jar and run.jar. JSPs fall over because they cannot import servlet-api and jasper classes - we fail the testsuite. Can you think of a reason why the CLs passed to Jetty on deployment of these two ears should be so different. (I'm pretty certain that watchdog has no ejbs), How should I approach this (aside from telling people to precompile their JSPs). Jules P.S. I added MBeanClassLoader.getURLs() which delegates to ServiceLibraries.getURLs() ? so that I could make up this path - was this a bad idea ? __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
