Nick,
I only disable caching when I run the project locally via the eclipse
plugin. But once deployed to my jetty test server I don't have any
-Dorg.apache.tapestry.disable-caching=true or the corresponding
<property>
settings. I also remember that I tried to fix a small change on the test
server and it didn't show so I am pretty sure that caching is on on the
test server (it's the default, right?).
Can caching cause this weird problem? Is there a better way to have my
library call a method on the visit class?
Thanx,
Andreas Pardeike
On 20 jun 2006, at 10.14, Nick Westgate wrote:
Hi Andreas.
Is Tapestry page caching enabled or disabled?
Cheers,
Nick.
Andreas Pardeike wrote:
Remember, it works fine for any time I run and test this up to the
point where I leave the test server running for 1 or 2 days and then
the first call to a page that contains this component will fail.
Andreas Pardeike
---------------------------------------------------------------------
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]
