> From: James Adams [mailto:[EMAIL PROTECTED] > To further clarify what I want to do, in case it will > lead to more pointed suggestions - 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
IMO, the JSP is *way* too late to be deciding whether the person is allowed to be there or not. A Filter catches the request on the way in, and it never gets anywhere near your Struts code, much less the JSP. (You are running all requests through an Action first, and not allowing direct access to JSP's, right?) I prefer the Filter because it's not Struts specific. It just looks for a cookie or looks for something in the request or session, and either lets the request pass through or redirects elsewhere. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
