fair enough. Used to see something similar on earlier versions of tomcat on
windows (been on 4.0.4 on linux for a while).
Reload of jsps worked for the most part but very occasionally we had to
delete tomcat's work directory and restart for changes to be compiled :(
If you can, upgrade to 4.0.4 (or 4.1.10 if you're braver than me).

I know you said the issue wasn't related to client side caching but here
goes anyway:

There are a quite a few posts in the archives about trying to get around
browser/proxy caching of pages.
We have a filter which sets http headers for each jsp requested:

<snip>
        if (response instanceof HttpServletResponse) {
            HttpServletResponse httpResponse =
(HttpServletResponse)response;
            httpResponse.setHeader("Cache-Control","no-cache");
            httpResponse.setHeader("Pragma","no-cache");
        }
</snip>

some people on the list have also used:

httpResponse.setDateHeader("Expires",0);

(although i'm not sure what the http spec says about 0 as a value, i'll look
it up one day)

Hope this helps,

Jon

-----Original Message-----
From: Dominik Jednoralski [mailto:[EMAIL PROTECTED]]
Sent: 17 September 2002 14:32
To: Tomcat User Help
Subject: RE: RE: Reloading .jsp-Pages


The problem arent the includes, its the jsp-page itself.
its no browser-cache-problem (i've deleted the cache before
reloading).

the timestamp of the jsp-file is definitly younger than the
version before. i deleted the file, restarted the server,
got my 404, copied the file again, restarted the server. guess:
still from server-cache...

i guess the 'reloadable'-switch doesnt work for some reason...


-----Urspr�ngliche Nachricht-----
Von: jon wingfield [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 18. September 2002 15:21
An: Tomcat Users List
Betreff: RE: RE: Reloading .jsp-Pages


... and if you are only changing included files then touch the jsp doing the
include

-----Original Message-----
From: Dominik Jednoralski [mailto:[EMAIL PROTECTED]]
Sent: 17 September 2002 13:47
To: Tomcat User Help
Subject: RE: RE: Reloading .jsp-Pages


thats the point: it doesn't recompile even if the files where updated.
isn't there a switch to force tomcat to always recompile all jsps?

-----Urspr�ngliche Nachricht-----
Von: Barney Hamish [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 18. September 2002 14:34
An: 'Tomcat Users List'
Betreff: RE: Reloading .jsp-Pages


Usually you need to touch the files updated files somehow after copying them
otherwise tomcat doesn't know that it needs to recompile them. An
alternative is to delete everything in the work directory and restart tomcat
forcing it to recompile all jsps.
Hamsih

> -----Original Message-----
> From: Dominik Jednoralski [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 17, 2002 2:29 PM
> To: Tomcat User Help
> Subject: Reloading .jsp-Pages
>
>
> Hey,
>
> I'm using tomcat 4.0.1 / windows. I've a problem with reloading my
> jsp-pages.
> tomcat simply ignores the changes I've made to them. I added
> the following
> contexts
> in the server.xml-file:
>
> <Context path="/WEB-INF/classes/myWebApp" docBase="myWebApp" debug="0"
> reloadable="true" />
> and
> <DefaultContext reloadable="true" />
>
> Anyway, they're still in the servers cache and aren't
> reloaded after an
> update.
>
> Does anyone of you smart guys know how to tell tomcat to
> always recomlpile
> the jsp-files and
> -includes in the MyWebApp-Directory? Thank you...
>
>
> Dominik Jednoralski
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>

--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to