You can probably add some sort of hivemind interceptor to the typical core engine services (direct / page / etc ) to listen for page changes on a per user basis. It could get a little sticky in a lot of scenarios. (Such as handling different session persistence strategies - but if it's just for one app I guess it won't matter).
I almost added a central hivemind service to expose those page listener methods as global listeners you can have a hivemind service implement to generically listen to all page changes (for all pages) but decided not to because it wasn't the right solution for the bug I was trying to fix...If you file a jira issue I could probably do it pretty easily. (Can't promise when though) On 1/2/07, Dennis Sinelnikov <[EMAIL PROTECTED]> wrote:
Hey guys, I've searched and searched, but nothing too appealing popped up. Ideally, I would like to attach a listener to SomePage.java class. This listener would get fired when a user is leaving the current page. In this listener method, I would simply reset some of the persistent session properties. Thoughts? Prayers? -Dennis --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
