Andreas, I went back and forth with another developer on this list less than a month ago about some of the pros and cons of subclasses, pageValidate, and interceptors for authentication. You might want to take a look at that thread.
http://mail-archives.apache.org/mod_mbox/jakarta-tapestry-user/200603.mbox/[EMAIL PROTECTED] This puts you in the middle of the thread where Ryan suggest that I use the pageValidate method instead of interceptors. -Mike On 4/9/06, Marc Ende <[EMAIL PROTECTED]> wrote: > Hi Andreas, > > > [...] > > What about the Hibernate Interceptors, the Hibernate Event > > interface, perhaps a self-coded Hivemind interceptor solution, > > some Tapestry stuff I don't know? How did you solve this > > problem? > > > I'm really looking forward to all of your answers! ;) > > I'm using the validation method to validate protected parts of the > website. > > I've extended the BasePage to a general WebsitePage and after that > there is a subclass AdminPage. In this page I've implemented the > validation. If I'm building up a new site, wich should be protected > I'm just extending the AdminPage. After that I'm sure that I only have > authorized users on the site (If I haven't overridden the validate > method without a super.validate(..)). > > That might be a newbe-way, but it's easy to implement and works... :) > > yours > > Marc > > > -- > Mit freundlichen Grüßen > Marc Ende > mailto:[EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
