But if you do not have access to filters, this might be a good way to do it. ----- Original Message ----- From: "Stefan Krompaß" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, April 03, 2003 10:35 AM Subject: Re: About the <checkLogonTag> of the example application
> "Struts Users Mailing List" <[EMAIL PROTECTED]> schrieb am 03.04.03 17:27:26: > > > > > The <checkLogonTag> of the Struts application checks > > > if the user has logged in the application before > > > displaying a JSP page. > > > Therefore it manages a part of the security of the > > > application. > > > I would like to know if this tag is a good practice ? > > > If it can be used in a "real world" J2EE application ? > > > If it is J2EE compliant and MVC compliant ? > > > > I think that right before you display a JSP is *way* too late to be checking > > to see if someone is logged in or not. I do it in a Filter and they never > > even get to the ".do" Action if they haven't logged in. > > > > -- > > Wendy Smoak > > Applications Systems Analyst, Sr. > > Arizona State University PA Information Resources Management > > > > Could you please give an example for that? > > Stefan > ____________________________________________________________________________ __ > Mit der Multi-SMS von WEB.DE FreeMail koennen Sie 760 Zeichen versenden. > Informationen unter http://freemail.web.de/features/?mc=021184 > > > --------------------------------------------------------------------- > 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]
