Hi Casey,
I agree, resolving class loader problems is not easy. But it does have a
bit of logic :-)
The solution you found ( put everything in common/ ) is ok - that's how
tomcat worked in 3.2 and before, and still works.
Resolving the problem with a separate class loader for container is a bit
Hi Casey,
Welcome to the wonderful world of ClassLoading.
The default configuration for 3.3 is to use a separate class loader for
container ( i.e. tomcat.core, jasper, jaxp ) and web applications.
This resolves a number of problems - like having a different parser in the
web application.
It
On Fri, 9 Mar 2001, Casey Lucas wrote:
> So, given all that, I need to control lifetime of TagHandlerPoolManager's
> default instance. By controlling it, I can have one TagHandlerPoolManager
> instance per web application and when the web application gets unloaded,
> all the Tag.release methods
Hi Casey,
This is a hard question :-)
The main decision you must make is that:
Do you want to use JspServlet or JspInterceptor ?
The first solution ( using Jasper via JspServlet ) is what is used in
tomcat 3.1, 3.2 and 4.0 - and it has the big advantage that the full
Jasper in interfaced usin
