I agree with you here, but I say to each his/her own. I think a better way to do this would be to build plugins for tools to manage your validation files... Or just do them by hand. Same with Hibernate mapping files... They're so easy, I never understand why someone wants to generate them.
Hear hear! To each his/her own :)
I can't understand why someone wants to write XML that mirrors code either. I especially don't like trying to keep things in sync and have to think of all the places in XML I have to change when I add a new field to a form or refactor classes into new packages and such. XDoclet makes me more productive in these respects.
The XML generation by Xdoclet does provide one (questionable) advantage... If you really needed to, you could put a jar file with updated validation xml files in the classpath of your servlet container and override the validation files in your war file :-)
But this is not something XDoclet helps with. You could do this without XDoclet, of course - just maintain two validation XML files.
Why folks need to make validation so dynamic I still have yet to understand. If my forms change, validation changes. They are intimately tied in the applications I've been working on. I certainly am not so close-minded to think that my apps are generically representative, so that is why I think flexibility in how folks work is important. To each his/her own.
Erik
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
