--- Mufaddal Khumri <[EMAIL PROTECTED]> wrote: > In Struts1 I did have a Base Action that I extended from along with a > session scoped variable that kept track of whether the user is logged > in or not. This functionality is needed by multiple actions who ended > up extending the base class. Since Struts 2 has interceptors, I felt > that it would be a better design to create an interceptor that does > this and that way the Action does not have to extend a base class.
The point is, more or less, what Ted and Al said: having the interceptor check that the user *was* logged in correctly is fine, and is a valid use--checking for a logged-in user is a cross-cutting concern. Logging in itself *isn't*, so belongs in an action. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
