Todd, No big ones that I can come up with, other than what Vic was trying to stress about letting the container do the work for you. My comments to Rick were about a specific problem with putting it into the Actions, due to the order of events that take place to process a request. I was just trying to remind Rick that in most cases, the Action is way to late in the process. I think there are several ways to skin this cat.
Chuck At 08:19 AM 6/4/2002 -0400, you wrote: >I have to ask a question; Why not use a filter to handle this? The filter >will be called before any components of struts are invoked. It has access >to the request, response and session and can handle forwarding the request >to the login page or error page if they are not currently logged in. If >container managed security is used, it will get invoked prior to the filter, >which can then check the getRemoteUser() and the session to ensure that they >have been logged in and perform any setup that is required for creating a >user object and storing the information in the session or wherever. The >filter can then chain to the requested page with the chain.doFilter(). > >Any reason not to do this? > >Todd > >-----Original Message----- >From: Galbreath, Mark [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, June 04, 2002 7:56 AM >To: 'Struts Users Mailing List' >Subject: RE: related to: Re: #2 - Use DispatchAction to organize related >operations > > >Chuck is absolutely correct on the linear progression of action processing. >I, too am overriding processPreprocess and it works beautifully. Besides >increasing security, it cuts down on unnecessary CPU bandwidth. > >Mark > >-----Original Message----- >From: Chuck Cavaness [mailto:[EMAIL PROTECTED]] >Sent: Monday, June 03, 2002 10:58 PM > >Rick, > >catch this earlier. I had implemented something along these lines awhile >back and soon remembered that the ActionForm is populated and the >validate() method is called, all of this before the Action's execute() >method is invoked. The question is, do you want to check whether or not the > >What I suggest is to look at the processPreprocess() method in the >RequestProcessor and possibly override this to do your checks. It's called > >Just some things to think about, >Chuck > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > > > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
