Marc,
This is probably not a priority, but would make my life a lot easier. I am revisiting JSPs. Short of rewriting tools.jar, the easiest way for me to get JSPs to compile properly in Jetty/RH is the following: Walk up my WAR's classloader hierarchy, as far as I think necessary, putting together a list of the URLs of every dir/jar referenced. copy remote resources to a tmp dir, and convert all items in path to a filename. kick off javac with classpath thus set. The following features would make my life a lot easier if supported by your new ScopedClassLoader: 1. named scopes - i.e. EAR, WAR, EJB-JAR, J2EE-PLATFORM, EXTENSIONS, etc... 2. ability to retrieve, for a named scope, the complete list of URLs for it's jars/dirs The naming stuff is not essential, but a convenient means of differentiating the different groups of classes that will be picked up by the classloader during it's lifetime. Or have I misunderstood scoping ? Jules _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
