{
myExecute(){
..
}
}
What do experts recommend??
Regards
Felipe
-Mensagem original-
De: Gopal Venkata Achi [mailto:[EMAIL PROTECTED]
Enviada em: quinta-feira, 4 de dezembro de 2003 18:55
Para: Struts Users Mailing List
Assunto: RE: Subclassing ActionServlet
Hi
I have come
: Subclassing ActionServlet
Hi
I have come across a plug-in for Struts, that is called as SAIF (Struts
Action Invocation Framework), which enables us to write a pre-action and
post action methods. You can use PreAction method for doing all the
session authentication, etc., I did not really use
Para: Struts Users Mailing List
Assunto: Re: RES: Subclassing ActionServlet
This way you can't extend other 'struts core actions' (Dispatch,
Lookup...).
I think a better way may be:
- Using a filter (servlet 2.3) in order to pre and post process the
request
- Extending RequestDispatcher
Regards
All,
I need to check the Session for an authenticated user before most requests.
To do this I subclassed ActionServlet and only call super(request, response)
upon verification that authenticated user is in the Session.
if (request.getRequestURI().endsWith(welcome.do) |
Does anybody know of any serious disadvantages or side effects of
subclassing the ActionServlet class rather than the RequestProcessor
class.
The most obvious would be that your changes in the ActionServlet would
apply to all modules, while RequestProcessors are per-module; also, you
have less
Errr. request processor might be upgraded in version 2.0 of Struts.. so
I subclass Action.
.V
Fullam, Jonathan wrote:
All,
I need to check the Session for an authenticated user before most
requests.
To do this I subclassed ActionServlet and only call super(request,
response)
upon
Jonathan Fullam
I need to check the Session for an authenticated user before
most requests.
Have you ruled out using a Filter for some reason? In my project, I
found that inside the Action was too late to be checking whether the
user is allowed to be there or not.
--
Wendy Smoak
List'
Cc:
Subject: Subclassing ActionServlet
All,
I need to check the Session for an authenticated user before most requests.
To do this I subclassed ActionServlet and only call super(request, response)
upon verification
ActionServlet.
Regards
Jim.
- Original Message -
From: Kevin Robair [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, June 06, 2003 2:31 PM
Subject: Re: Subclassing ActionServlet
I just did the same thing, but had no problems. Here
is what I did:
public class
Hi,
I have just modified an application where I now subclass ActionServlet. The
problem is my JSP's that use resources now throws an exception about not
being able to find the key. Are there any issues with subclassing
ActionServlet that I should be aware of.
Thanks
Jim
. The
problem is my JSP's that use resources now throws an
exception about not
being able to find the key. Are there any issues
with subclassing
ActionServlet that I should be aware of.
Thanks
Jim.
-
To unsubscribe
: Thursday, May 24, 2001 10:38 PM
To: [EMAIL PROTECTED]
Subject: subclassing ActionServlet?
Hello struts-users,
My webapp needs bunch of beans that should be available
all the time and accessible from all JSP pages, so I guess I
have to create the beans at the startup time and set them
Hello struts-users,
My webapp needs bunch of beans that should be available
all the time and accessible from all JSP pages, so I guess I
have to create the beans at the startup time and set them to
the application context.
How should I do this? My candidates are,
1) create a subclass of
I made a sub-class of ActionServlet an overloaded the initXXX()
method that created the connecion pool. I did this because
my database manager beans needed access to the connection
pool parameters.
The other choice is to use something like a singleton or factory
bean pattery that generates the
14 matches
Mail list logo
