On Wed, Aug 20, 2008 at 2:45 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> Using exceptions for control flow was never one of Tapestry great > ideas; that's why its gone in Tapestry 5. Exceptions are exceptions, > representing things that have failed. > > In any case, the activate event is a good place to perform checks. > The return vaslue from onActivate() (the name of the event handler, > following the naming conventions) can be another page in the > application. So instead of throwing a redirect to the Login page, you > just return an instance of it. May i ask you what do you think about methods to restrict page view implemented in the wiki which have been adopted by chenillekit-access module? I mean in an absolute manner and also compared to onActivate() from a RestrictedBasePage Regards -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
