On Wed, Feb 24, 2010 at 2:24 PM, Algirdas <algirda...@gmail.com> wrote: > > Well, because I want to redirect from other places in code, not from > onActivate() method.
I think this is a good course. I think you'll find your pages more maintainable when you have this kind of organization in place. If you have to get mid-way through processing or rendering the page to discover that the user doesn't belong there ... well, that would be a design smell to me. It's also very common to contribute a ComponentRequestFilter to the ComponentRequestHandler service for this kind of global concern; you can place an annotation on your page classes that control the behavior. This is how I've done simple page-level access security. > > But I see now it should be possible to redesign a bit to achieve required > redirect from onActivate(). > -- > View this message in context: > http://n2.nabble.com/Redirect-not-from-onActivate-tp4627871p4629010.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
