Jim, What you really want to achieve is best done outside Struts. Basically you are trying to achieve two things:
1)First, a user not logged in should be forwarded to a login page. 2)Second, prevent unauthorized users from not accessing the page. This is best done by using J2EE security. Use j_security_check in your login page and associate the logged in user with a role. Protect the resources by associating them with that role. Add a <login-config> to web.xml so that users who are not logged in, are automatically forwarded to login page. >From your second part of the description that you want to stay in the same page when logged in - it seems you are using JSP Model 1 Architecture. But anyway, if the above security model is implemented, you dont need any filter, RequestProcessor extension or Struts Action. Your problem is solved. In your JSP, just point the link or button or form submission always to the same JSP. If the user is not authenticated J2EE container security will forward to login page. If not you will continue to stay in the same page Hope that helps, Srikanth Shenoy ============================== Author: Struts Survival Guide ObjectSource Publications http://www.objectsource.com ============================== >>I am including this session validator on each JSP of >>my application to check to make sure that a user is >>logged in, and if not I forward to the login page. >>There really is no logic involved other than >>if (loggedIn) >>{ >> // stay on current page >>} >>else >>{ >> // go to login page >>} --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
