David Winterfeldt writes: > I don't think there would be anything wrong with your > idea, but I think it is a little more flexible keeping > the validation separate from the ActionForm. I > started working on a validation framework, but I put > the info in an xml file. I would rather change a > value in an xml file than having to recompile my code. > > > * It makes the validation rules more accessible to > less technical people. One day the XML might tie into > a JSP editing tool to provide easy access and editing > of the validation rules. I've been thinking of doing something similar for the logic rules associated with business objects. For example, consider an Employee class where the logic to calculate the bonus is based on some of the other attributes of the object (i.e. jobcode, location). It would be useful to define these rules in XML to facilitate maintenance as you point out for validation rules. -- Nick
- server-side, java-based validation rules for struts.. Levi Cook
- RE: server-side, java-based validation rules for st... Cook, Levi
- Re: server-side, java-based validation rules for st... Jonathan
- RE: server-side, java-based validation rules for st... David Winterfeldt
- Re: server-side, java-based validation rules fo... Ted Husted
- RE: server-side, java-based validation rules fo... Nick Afshartous
- RE: server-side, java-based validation rules for st... Cook, Levi
- Re: server-side, java-based validation rules for st... Levi Cook
- Re: server-side, java-based validation rules fo... David Winterfeldt
- Re: server-side, java-based validation rules for st... Jonathan Asbell
- Re: server-side, java-based validation rules for st... Levi Cook
- RE: server-side, java-based validation rules for st... Cook, Levi
- RE: server-side, java-based validation rules for st... Cook, Levi
- RE: server-side, java-based validation rules for st... Cook, Levi