Jules, I can see the javax.servlet.jar on the JSP classpath returned from AbstractWebContainer.getClassLoaderURLs - what jboss version are you using? Caveat: I haven't refreshed my tree in the last 3 days or so, so maybe there has been a recent change ...
Jan Jules Gosnell wrote: > I am trying to crush the two JSP compile errors in this testsuite. > > The classpath for Jasper is being built by walking up the classloader > hierarchy from the WebApp to the top, passing each classloader to > AbstractWebContainer.getClassLoaderURLs(ClassLoader). > > My problem is that the javax.servlet.jar does not seem to have been > loaded by an immediate parent of my webapp's classloader. > > You will want a fixed width font to view this. > > > sun.misc.Launcher$ExtClassLoader@7d8483 > | > | > sun.misc.Launcher$AppClassLoader@7fdcde > | > | > java.net.URLClassLoader@6930e2 > | > > -------------------------------------------------------------------..... > > | | > org.jboss.system.UnifiedClassLoader@76949770 > org.jboss.system.UnifiedClassLoader@806b8bd7 (JAVAX.SERVLET.JAR) > | > | > java.net.FactoryURLClassLoader@5ef658 > | > | > org.mortbay.http.ContextLoader (MY WEBAPP) > > > Consequently the servlet jar does not get onto the classpath and JSP > compilation fails..... > > > So what should happen here ? > > Should a UnifiedClassLoader return all it's siblings URLs as well - they > are all loaded into a flat scope and are available to each other, are > they not? > > > > Thanks for your time, > > > > Jules > > > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
