You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Remy Maucherat <rm...@mageos.com> on 2003/05/22 10:23:45 UTC

Re: cvs commit:jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/servletJspServletWrapper.java

>Jan,
>
>thanks a lot for the patch. Do you think this could help in fixing issue 
>19219 ?
>
>http://issues.apache.org/bugzilla/show_bug.cgi?id=19219

I don't know, and I didn't try yet. Possibly. The idea is that you
cannot reliably overwrite JAR on a running application currently (on
Windows, you can't right now), because the CL keeps them open.
Obviously, if Jasper (or some other component of the application) also
does bad stuff, it won't help.

I plan to fix the CL part of the problem when I start working on the
deployer.

Maybe a generic solution would be to:
- copy the JARs to the work directory on startup
- the CL will use the JARs from the work directory
- if requesting a URL to a .jar in /WEB-INF/lib using getResource,
cheat and return a file URL to the stuff in the work directory (I
wasn't planning to do that; this could possibly have bad consequences,
a!
nd it does
n't comply with the spirit of the spec IMO)

Rémy



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org