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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
