> I don't understand why you think this is better. With validation.xml, all my > validation requirements are in one place; I don't have to look a number of > java form files to find out what they are. And if any of them change I only > have to edit one file, and restart struts; without needing to recompile my > application. > > Please explain how this framework provides any added value.
The reason that I made this framework was because I had to do some conditional validation. Depending on other field values or some other conditions, some fields were sometimes required and sometimes weren't. This was hard to do with XML configuration files. And, if you have lots of large forms in your application, validation.xml tends to be very long and it gets hard to find what you need, so personally I like to define the rules in the form bean itself. > > Dave Derry > > > -- > To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> > -- Shinya Kasatani <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
