username and password store
every time a request comes in.
-Original Message-
From: Mufaddal Khumri [mailto:[EMAIL PROTECTED]
Sent: 04 January 2008 04:48
To: Struts Users Mailing List
Subject: Interceptor best practices ...
Am trying to understand the best practice if any
The best use of interceptors is for behavior that will be shared by
several Actions. If there are several different places where a client
might be authenticated, then, in that case, a login interceptor (and a
custom interceptor stack) can be a good idea.
When coding an Interceptor, you can just
--- 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.
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
Am trying to understand the best practice if any for a
ValidateLoginInterceptor of sorts. In the code below, if the login is
valid then we make a call to:
return actionInvocation.invoke();
In case the login information was incorrect, what should one do?
return ActionSupport.ERROR
5 matches
Mail list logo
