Look at the source code of the ResetService and implement your own
service which does just that, but with the needed security constraints.
A Tip: don't use inheritance (from the ResetService implementation) but
instead copy-and-paste. This might feel silly but its the recomended
way, since tapestry services are not designed for inheritance.
You will probably come with the question: why are all those members
private and not protected.
The answer is one sentence before.
Cheers,
Ron
Christian Mittendorf wrote:
The ResetService is indeed the kind of functionality that would help.
But it's not an option. You have to enable or disable this feature for
the application at startup. And if you enbable it, everybody can call
the service url and use it for "refreshing" your application.
As it is written in the java docs, that's not the kind of functionality
that someone would like to have in a live application.
Christian
Am 06.01.2006 um 14:39 schrieb Bryan Lewis:
How about the ResetService? I haven't tried it in 4.0 yet but it sounds
right: "ServiceLink used to discard all cached data (templates,
specifications, et cetera)."
Christian Mittendorf wrote:
The html part was updated and the method "BaseEngine.clearCachedData"
is invoked to update the page cache and put the changes live.
How can we accomplish such a behaviour with Version 4 of Tapestry?
---------------------------------------------------------------------
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]
