To be extremely sure you are looking at your most
recent .jsp, simply introduce an error in your jsp
example forget a semicolon and save the page to the
server.
Request for the page, obviously you will see the error
page if you have one or tomcats error page. Now return
to your jsp page and remove the intentional error then
request for the page again, this time you are sure you
will see the latest copy of your .jsp.
I've used this not so clever technique on .asp on IIS.
And works just fine.
Allan Kamau.
Nairobi.
--- Franky Tong <[EMAIL PROTECTED]> wrote:
> It is not a browser-cache problem because I have run
> the jsp file in
> several machines.
>
> What is tomcat-not-recompiling-source problem?
>
> "Samson, Lyndon [IT]" wrote:
>
> > You need to find out if its a browser-cache
> problem, or a
> > tomcat-not-recompiling-source problem.
> >
> > -----Original Message-----
> > From: Franky Tong
> [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, May 09, 2001 9:42 AM
> > To: [EMAIL PROTECTED]
> > Subject: Problem in refresh the new jsp file
> >
> > Hi all,
> >
> > I have a problem that I get an outdated JSP page
> even if I have updated
> > the JSP file in the server. It shows me the old
> content in the browser
> > even I have refreshed the page.
> >
> > Is there something that I need to set about the
> caching?
> >
> > Thanks!
>
> --
> Data Center,
> Global Infrastructure Solution Team (GIS)
>
> Direct Phone : 2666 8364
> Pager : 7203 2006
> Mobile : 9373 0760
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
