No, JVM system properties are specified on the java command line, using the -D option.
----- Original Message ----- From: "Luis Neves" <[EMAIL PROTECTED]> To: "Tapestry Developer" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, May 17, 2002 5:24 AM Subject: Re: [Tapestry-developer] Two quick questions > > [EMAIL PROTECTED] wrote: > > > This is in the manual, but probably belongs in the FAQ. > > There's a JVM system property, > > com.primix.tapestry.disable-caching (I think -- check > > manual) that disables all caching of pages, specs, > > templates, scripts, etc. > > It's official .. I'm lame... I'm still wrestling with this. > According to the documentation of AbstractEngine : > > com.primix.tapestry.disable-caching > > "If true, then the page, specification, template and script > caches will be cleared after each request. This slows things > down, but ensures that the latest versions of such files are > used. Care should be taken that the source directories for > the files preceeds any versions of the files available in > JARs or WARs." > > Which is exactly what I want during development. So I put the > following in the *.application file: > > <property name="com.primix.tapestry.disable-caching">Boolean.TRUE</property> > > But that doesn't work. I keep getting the "old" version of > the pages. > > So my guess is that I have to set this property elsewhere, > but where? > My understanding was that system-properties were set on the > *.application file. > > Thanks, > > > Luis Neves > > > > > > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
