One possibility yes, but that approach requires to keep a list of secured pages to allow un-authorized users access non-secure pages.
(Pages could of course be annotated to be secure or use marker interface.) And your approach occurs earlier in the request cycle... Thanks for the pointer! -99 (Always nice to do things right and to learn :)) Thiago H. de Paula Figueiredo wrote: > > Em Wed, 20 Aug 2008 08:23:12 -0300, 9902468 <[EMAIL PROTECTED]> > escreveu: > >> I have also noticed that onActivate is a bad place to check general >> access rights as you cannot be sure that the check implemented to base >> class is not overridden or if developer uses one of the >> onActivate(param) variants, your check might not get called at all. > > Wouldn't a RequestHandler or Dispatcher be a better place to do these > checks? > > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Trying-to-Implement-RedirectException-in-Tapestry-5-tp19060597p19068531.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
