Henri,
I am referring to "Tapestry pages cache". As I understand it, Tapestry cache
the HTML templates after they were first requested. Hence, further
modification of the HTML pages (after it was cached) will not take effect.
Since, the particular HTML templates in my application is submitted (a
On 7/31/06, KE Gan <[EMAIL PROTECTED]> wrote:
Jesse, thanks for the fast reply (as always :))
If I were to use the ResponseBuilder approach, that means Tapestry will
cache the pages. And since the pages are submitted (and modified) by users
from time to time (as mentioned in earlier post), how
Jesse, thanks for the fast reply (as always :))
If I were to use the ResponseBuilder approach, that means Tapestry will
cache the pages. And since the pages are submitted (and modified) by users
from time to time (as mentioned in earlier post), how can I clear the cache
for a specific pages ? Is
I would take a look at the new ResponseBuilder interface provided in 4.1.
Though it's still possible to do in tapestry 4, the new rendering logic
would make it very easy for you to capture the output of a page render and
do whatever you like with it.
It's also something you can control with a hiv
Hi,
I am working on a Tapestry application that has over hundreds Tapestry HTML
pages, all sharing one single Java class file. These Tapestry HTML pages are
submitted by users from time to time ... so they are not immediately in the
web application, and they may change from time to time.
The thi
