-1 on giving too many options. The validation framework gives a way to do validations. You can also code your validations in Java, or build your own hooks into any other validation framework through interceptors.
Remember, while it seems nice to let people choose from an array of options for how to do something, it really ends up being confusing. Besides, they've already got a way to do validations in many more different ways than these... it's called Java. ;-) > Ted, scenario: > > You have a wizard form bean. You have 5 stages. Each > stage is a different validation. All use the same > action mapping and class. Do you really want to put > all 5 validations in the action mapping? I wouldn't > BUT... Why not allow both ways? Either-or thinking is > this file or that file, but we can do and-thinking > and allow the developer to choose what best fits his > design. I am +1 for your idea, as long as you allow > separate files too. > > Paul --------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=39135&messageID=77886#77886 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
