There is no JSP cache in Geronimo per se, other than the web app's
classloader. The first time a JSP is accessed the web container
generates java source for a servlet, compiles it into a class file in
a tmp work directory, and services the request. Then subsequent
requests are serviced by that class which is now linked into the
classloader. Restarting the webapp from the console or using bin/
deploy.sh will reinitialize the classloader, but I doubt that is the
underlying cause for the stale data you see. More likely you have
made some change to the JSP source and aren't seeing that change
reflected when you reload the JSP? If that's the case then you need
to redeploy the webapp when you make changes to the JSP:
bin/deploy.sh redeploy mywebapp.war mygroup/myapp/1.0/war
It might be easier to use the hot deploy directory to automatically
redeploy your app when a JSP changes but I have less experience with
that.
Best wishes,
Paul
On Oct 12, 2007, at 2:30 PM, MShah wrote:
Is there a way to purge the jsp cache in geronimo like in weblogic
where in a
few files from the filesystem needed to be purged? Please let me
know as
the file that shows up still has old data, but the file seems to
have been
deployed on the server correctly. Any inputs will be appreciated.
M.Shah
--
View this message in context: http://www.nabble.com/Geronimo-jsp-
cache-purging--tf4614208s134.html#a13177081
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
