Exactly what do you need this for?
If you don't need any Tapestry logic, there might be other ways to do it -
like a servlet filter or a threaded service that implements Discardable.
On Tue, 19 Sep 2006 21:58:20 +0200, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
It might not be super fun to learn, but I think the "tapestry" way of
doing
this would be to contribute something to the WebRequestServicerPipeline
so
that you know definitively when the cycle ends regardless of what
services/engines are involved..
http://tapestry.apache.org/tapestry4/tapestry/hivedocs/config/tapestry.request.WebRequestServicerPipeline.html
On 9/19/06, Dobrin Ivanov <[EMAIL PROTECTED]> wrote:
Hi,
I want some advise of which is the best way to catch
the end of the request cycly. I have tried it using a
PageDetachListener, but the problem is that sometimes
there is more than one page involved into the request
cycle and then I get more than one invocation on the
pageDetached(...).
So I'm wondering if overriding the Engine's
service(...) method is the best place?
Thanks and best regards,
Dobrin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
