Hi,

there is still a problem with shared classloading in current jBoss.

Tomcat fails to compile any JSP file which references a class that is
only available from the application classpath, ie. the shared
classpath which is constructed from Manifest-Classpath entries during
EAR deployment. It seems, that javac is called with the wrong
classpath. It only includes the WAR and jars from WAR!/lib. 

After tracing a JSP request in the debugger, I saw that the various
jboss-interceptors were called properly and the Thread
contextClassLoader was set to the jboss' loader. The problem is, that
to call javac Jasper has to construct a command line option for the
classpath, but there is no way to get the String representation of the 
contextClassLoader's path.

Any ideas?

Gabor
-- 
Gabor Herr                           [EMAIL PROTECTED]
Computer Science Department          [EMAIL PROTECTED]
Darmstadt University of Technology
Germany

Reply via email to