Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@apache.org Received: (qmail 79192 invoked from network); 24 Dec 2002 08:41:24 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 24 Dec 2002 08:41:24 -0000 Received: (qmail 1830 invoked by uid 97); 24 Dec 2002 08:42:32 -0000 Delivered-To: qmlist-jakarta-archive-struts-user@jakarta.apache.org Received: (qmail 1813 invoked by uid 97); 24 Dec 2002 08:42:31 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Struts Users Mailing List" Reply-To: "Struts Users Mailing List" Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 1801 invoked by uid 98); 24 Dec 2002 08:42:31 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <341F8F7FCD8AD5118FD300306E06BB6507DBCD53@HO-MS1> From: Mohan Radhakrishnan To: Struts Users Mailing List Subject: Login filter Date: Tue, 24 Dec 2002 14:09:03 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I wanted to clear a doubt about this. Do I remove the conventional login check from my LoginAction to the filter ? That seems to be the right way to use a filter. 1. Check for the user container( username,password object ) in the session. 2. Call the isNew() method of the session. The first method might be like this. session = req.getSession( true ); if( session.getAttribute( WebConstants.USER_KEY ) == null ){ session.getServletContext().getRequestDispatcher("login.action"); } else{ chain.doFilter( req, response ); } What about the second method ? I need to restrict the login action from being filtered itself. Any advice is appreciated. Thanks, Mohan -- To unsubscribe, e-mail: For additional commands, e-mail: