hmmm...we actually never use the automatic validation in Struts, preferring to call validateXXX() methods in the ActionForm from the Action (creating and adding to ActionErrors objects), so we can redirect to different pages for different errors (potentially). So the first thing that gets called using this approach is our Action base class's perform() method, yes? This is where we enforce security, and then defer validation calls, redirection, etc., to sub-classes.
> 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. By cutting down on CPU bandwidth, do you mean just because the ActionForm validate() method will never be called for an unauthenticated user? peace, Joe Barefoot > -----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]>
