Hello, Sven.
Try setting Context.reloadable to true, restart Tomcat, and see if that
works for you.
Sven Köhler [EMAIL PROTECTED] wrote in message
b2m0cd$9pb$[EMAIL PROTECTED]">news:b2m0cd$9pb$[EMAIL PROTECTED]...
I just checked the web.xml file in $CATALINA_HOME/conf/web.xml. It
suggests
I just checked the web.xml file in $CATALINA_HOME/conf/web.xml. It suggests
the development is the default mode in which Jasper operates. Have you
tried leaving development, reloading, and checkInterval out of your web.xml
file to see if the standard behavior works?
The tomcat-docs also state,
I just checked the web.xml file in $CATALINA_HOME/conf/web.xml. It
suggests
the development is the default mode in which Jasper operates. Have you
tried leaving development, reloading, and checkInterval out of your
web.xml
file to see if the standard behavior works?
The tomcat-docs also
It can take up to 15 seconds (default) for Tomcat to poll for changes to
class files. The frequency of how often Tomcat checks can be changed via
the Loader checkInterval property in the containing Context node. Ensure
Context.reloadable and Loader.reloadable are not set to false; they are true
PROTECTED]
Subject: Re: AW: modified jsp-files and jasper2
The page was uploaded an hour ago, but you still couldn't see the
correct page online. I checked the work-folder, and the jsp-page has
_not_ been compiled. the old .java and .class file was still
Have you compared the date of the jsp file
with the corresponding java and class file?
Maybe the old class file is newer than the jsp file?
i haven't done that yet, but as the date of machine is synchronized with
a time-server it should always be correct.
i have also deleted the whole
Another wild guess:
How is the upload done? What happens to the file date-time when uploading?
- Lorenz
i haven't done that yet, but as the date of machine is
synchronized with
a time-server it should always be correct.
-
Hi, Sven.
Down below...
- Original Message -
From: Sven Köhler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, February 14, 2003 02:04
Subject: Re: AW: modified jsp-files and jasper2
It can take up to 15 seconds (default) for Tomcat to poll for changes to
class files
On Fri, 14 Feb 2003, Sean Dockery wrote:
[ Aside: Does manager/reload fail if Context.reloadable=false? ]
No ... explicitly reloading via the manager webapp does not care wither
reloadable was set to true or false. Even when I'm developing a webapp, I
don't use the reloadable flag at all --
Hi Sven
Have you tried stopping and restarting Tomcat?
Sometimes it's also necessary to empty the browsers
cache and restart the browser.
Lorenz
-Ursprüngliche Nachricht-
Von: Sven Köhler [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 13. Februar 2003 13:18
An: [EMAIL PROTECTED]
Have you tried stopping and restarting Tomcat?
Sometimes it's also necessary to empty the browsers
cache and restart the browser.
Hitting the reload-button of my browser should help, but it doesn't.
Reloading the application through tomcat's manager-app solves the
problem, but that is not a
John
-Original Message-
From: news [mailto:[EMAIL PROTECTED]] On Behalf Of Sven Köhler
Sent: Thursday, February 13, 2003 8:10 AM
To: [EMAIL PROTECTED]
Subject: Re: AW: modified jsp-files and jasper2
Have you tried stopping and restarting Tomcat?
Sometimes it's also necessary
The web.xml file has settings for reloading jsp pages you might have to
change the settings you have there. Also your browser might be caching
the pages so you can also turn off browser caching.
For jasper settings see the docs
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html
Certified Delphi Programmer
SBD Consultants
http://www.sbdconsultants.com
- Original Message -
From: Sven Köhler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 07:52
Subject: Re: AW: modified jsp-files and jasper2
The web.xml file has settings for reloading jsp
14 matches
Mail list logo
