in which way do you start your tomcat? service / startmenu / console ? maybe you could give the console approach a try and set the flag manually. other approach could be to edit the catalina.bat file where you can set a lot of tomcat-specific properties and your own vm-properties. sorry but i am linux user and i have made bad experiences with "windows-click-click" solutions.
another approach is to extend the default ApplicationServlet and checking in the initializeApplication() method if the flag is really set. see http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/ApplicationServlet.html#initializeApplication(). so you know if the flag is set right or not, which is a very important information. Malin Ljungh wrote: > OK, so this is the key then... > > I use tomcat5w.exe "Configure Tomcat" tool. > On the Java tab I have Java Options: > > -Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat 5.5 > -Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat 5.5 > -Djava.endorsed.dirs=C:\Program Files\Apache Software > Foundation\Tomcat 5.5\common\endorsed > -Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat > 5.5\temp > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Djava.util.logging.config.file=C:\Program Files\Apache Software > Foundation\Tomcat 5.5\conf\logging.properties > -Dorg.apache.tapestry.disable-caching=true > > but that's obviously not doing the trick :-( > > Any suggestions? > > /Malin > > On 7/29/07, *Eckenfellner Klaus* < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > the only way to get this behavior you want (changes to html files are > applied without restarting tapestry), can be set with the > -Dorg.apache.tapestry.disable-caching=true flag. here a snippet > from the > tapestry documentation: > > If specified (as "true"), then the framework will discard all cached > data (specifications,>>> !!!! TEMPLATES = html files !!!!!<<<<, pooled > objects, etc.) at the end of each request cycle. This slows down > request > handling by a noticable amount, but is very useful in development; it > means that changes to templates and specifications are immediately > visible to the application. It also helps identify any errors in > managing persistent page state. This should never be enabled in > production; the performance hit is too large. Unlike most other > configuration values, this must be specified as a JVM system property. > > how do you set the flag? consider that it MUST be set as > system-property > and MUST be set before tapestry has started. > > > Malin Ljungh wrote: > > Klaus! > > > > I do not use WAR, it is a directory with WEB-INF and classes and lib > > directories and all that stuff. > > > > In development I have > > -Dorg.apache.tapestry.disable-caching=true > > but I have also set this on my standalone Tomcat (I think.... > have not > > verified that it works though) > > Is it this flag that makes it work it development? I thought it was > > about class loading but perhaps also effects the html files also > > (since they are loaded by the servlet) > > > > I use Tomcat 5.5 and Tapestry 4.1. > > > > /Malin > > > > On 7/29/07, *Eckenfellner Klaus* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > > how do you deploy your application, with a WAR-file or do > you copy > > webapplication-folder into webapp-folder of tomcat? > > is it possible that you have set > "org.apache.tapestry.disable-caching" > > during development (see > > > http://tapestry.apache.org/tapestry4/UsersGuide/configuration.html > <http://tapestry.apache.org/tapestry4/UsersGuide/configuration.html>)? > > which version of tomcat and tapestry do you use? > > > > > > > > Malin Ljungh wrote: > > > This is mainly about Tomcat but also about Tapestry > handling of > > html files. > > > > > > I'm using Eclipse and Tomcat for development - works fine! > > > Particularly, if I change an html file, the change will appear > > immediately > > > without reload of context. > > > > > > But - if I have standalone Tomcat server, and change the > > contents of an > > > html file under the deployment directory, > > > I need to do a reload of context for changes to appear. > > > > > > Does anyone know why this is so? > > > How can I make the changes appear immedeately in the > standalone > > server as > > > well? > > > > > > Please help :-) > > > Malin > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > > For additional commands, e-mail: > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
