That's ok. Yep, something else. Here's what's in my jsp page: <jsp:forward
page="/servlet/PageMill" /> It just forwards to the servlet. It's strange,
if you use the full path to either one you get the updated information
from the database. But if you access using that context I set in the
server.xml it loads the information from the database once and that's it.
It just keeps sending what was sent the first time. Looks to me like it's
not even accessing the jsp to get the info. Would the backgroundProcessorDelay setting
help any? I didn't understand the doc's very well on that.
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
"Lee, Paul NYC" <[EMAIL PROTECTED]>
10/09/2003 04:22 PM
Please respond to "Tomcat Users List"
To: 'Tomcat Users List' <[EMAIL PROTECTED]>
cc:
Subject: RE: Help root context problem!!!
Sorry, I misunderstood. So something else here is caching your page. Do
you have a webserver sitting in front of tomcat or just tomcat?
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 5:05 PM
To: Tomcat Users List
Subject: RE: Help root context problem!!!
Oh, no that's not it. It does recompile the code just fine. If you for
example call http://myserver/a-path/index.jsp it works fine. Then
index.jsp will forward to http://myserver/a-path/servlet/MyServlet and
that works just fine. Both path will reflect any changes of the dynamic
content from the database. But if you access the index.jsp using
http://myserver it will load the content the first time, which it gets
from the Servlet and the servlet get from the database. However, from that
point on the http://myserver path will keep showing the same content even
after changing it in the database. Basically it's only loading the
information from the jsp and caching it forever. But if you access the jsp
and servlet directly using http://myserver/a-path/index.jsp or for the
servlet http://myserver/a-path/servlet/MyServlet they both will reflect
the changes. For some reason the context is caching the last content send
and never let's it go even though the jsp and servlet show they have the
updated information in them. It's not the code that needs to be
recompiled, it's the dynamic content from the database that needs to
update.
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
"Lee, Paul NYC" <[EMAIL PROTECTED]>
10/09/2003 03:40 PM
Please respond to "Tomcat Users List"
To: 'Tomcat Users List' <[EMAIL PROTECTED]>
cc:
Subject: RE: Help root context problem!!!
Hi Justin,
The work directory contains the generated source code and compiled classes
for JSPs. When a JSP is first requested, Tomcat generates Java source code
for the JSP, and then compiles it. Both the source code and the compiled
class are stored there. Since you changed your context and didn't change
any code, tomcat may not have updated your work directory accordingly.
Try shutting down tomcat, deleting the contents of your work directoy and
restarting.
You should not have to do this everytime.
Regards,
Paul
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 4:25 PM
To: Tomcat Users List
Subject: RE: Help root context problem!!!
No, but what will that do for me? Would I have to do that every time?
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
"Lee, Paul NYC" <[EMAIL PROTECTED]>
10/09/2003 03:20 PM
Please respond to "Tomcat Users List"
To: 'Tomcat Users List' <[EMAIL PROTECTED]>
cc:
Subject: RE: Help root context problem!!!
Hi Justin,
Did you try deleting the contents of the work folder?
Regards,
Paul
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 3:41 PM
To: [EMAIL PROTECTED]
Subject: Help root context problem!!!
I'm having caching problems with Tomcat. Here's what I'm trying to do. I
have an app under the mapping of /PageWorks. In the context I have a
index.jsp that does a jsp:forward to a servlet that handles the request.
So to access the app you have to type http://myserver/PageWorks and it
works. But, I want user to be able to type http://myserver and the
/PageWorks/index.jsp with respond. So to do this I change the context in
the server.xml file to point to PageWorks instead of ROOT. This also
worked like I wanted, but the index.jsp is loaded from the /PageWorks app
once. Then from there on it sends the old content every time. The servlet
that this jsp is forwarding to changes and so does the jsp, but the
http://myserver always returns the old. If you access the servlet or jsp
using there full http://myserver/PageWorks path you get the new content
every time. I've tried all the client side cache tricks, but I know for
sure it's the server that's caching it. How can I get this to stop?
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
