I guess the decision boils down to how your application is going to be written. For a project I worked on couple of weeks back, I ran into a problem where one of my Actions needs to extend a class to inherit some functionality, but I was stucked because I need to extend my "AuthenticationAction" which handles all my user login stuff.
I can't extend from 2 classes, right? I then went on to research the RequestProcessor. I used tiles of Struts 1.1 in my project so what I did was I ported the "AuthenticationAction" code to say "AuthenticationRequestProcessor" and it extends "TilesRequestProcessor" which extends the Struts "RequestProcessor".
So it all depends on if you're gonna run into problems like this?
My 2 cents. Hope this helps.
Andy Richards wrote:
Hi
After deciding which approach to take and reading a few of my struts books about the controller object ; ) I am now confused as which is the most appropriate class to extend to perform my login functionality. David suggests extending the base action class, however i have read that the RequestProcessor class was added to struts1.1 to extend the ActionServlet. From what i can see this class handles all requests and one of its methods calls the appropriate action. Therefore which would be the better class to extend ActionServlet, RequestProcessor or Action. Any ideas.....?
thanks
Andy
On Wednesday 20 Aug 2003 2:41 pm, David G. Friedman wrote:
Dear Andy,
I'm doing the same thing you suggest. My approach is to extend the base Action (or any type of Action) class by adding a functon 'checkLogin'. It takes the 'request' as the argument, checks the session for a User bean, and throws an exception if the bean is missing or if the ID number on the bean is zero/unset. In my execute() method I make my first line 'checkLogin(request)' and it handles my authentication.
If you try this approach, keep in mind I'm using Struts v1.1 final so I can use exceptions.
Tonight I'm going to try switching it to an interface so I can use it to extend any action type by using 3 lines (and without sub-classing):
1. import com.mycompany.auth.LoginCheck; 2. public class MyAction extends Action implements LoginCheck 3. checkLogin(request) <--- 1st line from within the execute or DispatchAction, or LookupDispatchAction method, etc.
Regards, David
-------Original Message------- From: Andy Richards <[EMAIL PROTECTED]> Sent: 08/20/03 09:46 AM To: [EMAIL PROTECTED] Subject: login request
Hi, i have created a form and a action which checks to see if a user
exists in my database and if so a value object is placed into the session. What i am
unsure of is how to a action called everytime a request is made? Can i configure struts-config.xml to send all requests via an action to see if this session object exists, and if not redirect the user to the login page?
many thanks
Andy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
