You could also write a filter to check for a valid session. This gives you more control over quite a few issues. This is my particular filter.
Edgar -----Original Message----- From: Andrew Hill [mailto:andrew.david.hill@;gridnode.com] Sent: Thursday, November 14, 2002 12:37 AM To: 'Struts Users Mailing List' Subject: RE: Check log-in status Best practice is to make used of the Container Managed Authentication provided by your servlet container. -----Original Message----- From: Mohan Radhakrishnan [mailto:MohanR@;hclcomnet.co.in] Sent: Thursday, November 14, 2002 13:23 To: 'Struts Users Mailing List' Subject: Check log-in status Hi, Do you usually check if the user is logged-in in every action ? I can think of two ways to do this 1. Check the status in every action 2. Block the /context/xxx.action where 'xxx' is anything but 'login' Am I right ? Thanks, Mohan -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
checkLogon.java
Description: Binary data
-- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
