There must be a diagram that shows all the calls before it actually hits execute() method. There are quite a few.
If you have a base action you can override one of them processRoles seems to be a logical place... sandeep --- David Erickson <[EMAIL PROTECTED]> wrote: > Hi I am setting up my webapp for security, had a big > thread about it last > week, we've implemented filters to handle all the > static filters sitting > around, but would also like to put some security > into the struts actions > themselves. I'm trying to figure out where the best > place to implement the > checks would be, if I need to extend the class that > actually calls the > actions, or if I should extend the base action and > insert checks, or what > the best thing to do would be. Somehow each of the > actions needs to have a > name assigned to it to check against as well, and > the information will be > pulled from a user bean stored in the session > variable. > > Thanks in advance! > -David > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
