+1 David Winterfeldt wrote: > 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. I think the java.bean.VetoableChangeListenter would be a good thing in an helper bean that was populated by an ActionForm bean, but would violate the API contract for an ActionForm bean. The ActionFormBean is suppose to accept whatever the actor throws at it, and then perform validation. This way we can return exactly what they entered for correction. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel 716 737-3463. -- http://www.husted.com/about/struts/
- 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
