Hi,
Similar to how different servlets run in different classloaders scope,
we have written a web application (WAR File) that runs the applications
for each customer by creating a classloader per customer within the same
servlet context.
This means that all the dependent jar files of the project are NOT
placed under WEB-INF/lib, but instead under another folder where the
applications can be hot-swapped. While we successfully implemented
customer specific classloader, we run into problems when the servlet
forwarded the request to a JSP.
JSP apparently takes the class loader in which the WAR file is running
and NOT our classloader, inspite of setting
Thread.getCurrentThread().setContextClassLoader(CustomerSpecificClassLoader)
in the servlet before the request was forwarded.
I am now stuck after committing so far in the project and now unable to
find a solution.
Can you please advice me a way out?
Pat
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
