A little suggestion. Inside the interceptor, you can also put the User in the ActionContext or your own custom ThreadLocal so you can use that all over the stack for permissions/roles/etc as an alternative to say Acegi.
Cheers, Drew Kutcharian Venarc Inc. www.venarc.com ----- Original Message ---- From: Mark Menard <[EMAIL PROTECTED]> To: Struts Users Mailing List <user@struts.apache.org> Sent: Wednesday, April 18, 2007 12:36:21 PM Subject: Re: [s2]Would like each action to go throught my parent class On 4/18/07 11:11 AM, "Mark Menard" <[EMAIL PROTECTED]> wrote: > Now, with that example shown, I wouldn't use it. Look at an interceptor to > do this. I'm working on exactly this right now, a login interceptor. Stay > tuned for a write up when I get done. As promised here's a fairly complete write up of the process: http://www.vitarara.org/cms/struts_2_cookbook/creating_a_login_interceptor Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
