I don't think so, the reset service essentially is a method call to the
AbstractEngine:
engine.clearCachedData();
So enabling the service shouldn't make much difference, although
obvisouly when you use the reset service you're clearing all the cached
data, so Tapestry will re-read all the .page files and assets again.
For the record, my solution to the live change problem was to have a
page protected with a login/password that acutally got the engine
reference from the cycle, and calls the above method. That way, I keep
reset service disabled, keep the cache enabled, but I can reset it using
my own page.
HTH
Apache wrote:
Does enabling this have any performance hits?
[quote="Alexandr Kundirenko"]Hello Daniel,
Enable reset service adding this option:
-Dorg.apache.tapestry.enable-reset-service=true
Usage: http://localhost:8080/appName/app?service=reset&page=PageName
--
Dan Garland
------------------------
[EMAIL PROTECTED]
office: +44 (0) 207 803 1947
mob: +44 (0) 7979 770053
icq: 120963437
aim: dmgarland1767
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
