On 4/18/06, Eric Rank <[EMAIL PROTECTED]> wrote: > From reading a bit on Rick Reumann's site > (http://www.learntechnology.net/validate-manually.do) > a simple way to handle this is to call the validate method within the > execute method of the Action. There's a bit of logic that has to be > processed in order to capture errors, but it works pretty well. > However, I personally feel like it could lead to some sloppy "execute" > code.
Just curious what you think might be sloppy? One of struts biggest weaknesses is in the validation side of things. I just happen to prefer a consistent approach that is easy to understand, easy to debug, and easy to code - hence I call validation manually from my Action and don't ever use validate="true" in my action mapping. Extending the request processor in my opinion is a bad idea. One of the main reasons is it becomes very difficult for someone coming on to your project to figure out what is going on, since it's not typical to have to mess with that class. Obviously you have a lot of power if you want to start messing with that class, but I avoid it. I haven't been following the latest Struts 1.3 stuff as closely as I'd like so maybe someone else has some ideas that could help since I think they've introduced more interceptor/chain types of things that could aid in what you want. (Then again, I'm still not convinced all this injection stuff is all it's cracked up to be. The trend seems to be to make things so loosely coupled to the point that it's confusing to often figure out 'what is causing' what to occur. It gets annoying in my opinion to have to keep searching through different xml files to figure out what is going on </rant>). -- Rick http://www.learntechnology.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
