As Thiago said, the main pros of Tapestry Validator, is that everything is configured on the server side. So you will have a server side and a client side validations configured at once.
But, in fact, with all your requirements, you should use jQuery Validator. Just for your information, a tutorial for creating a new Validator : http://wiki.apache.org/tapestry/CreatingCustomValidators PS @Thiago : Try Tapestry5-jQuery, and you will love it ;) Manu 2012/3/8 Thiago H. de Paula Figueiredo <thiag...@gmail.com> > On Thu, 08 Mar 2012 13:56:04 -0300, George Christman < > gchrist...@cardaddy.com> wrote: > > I agree, it is pretty bulky and complex and I'm not opposed to using the >> tapestry validator, however I haven't found much documentation on how to >> create custom tapestry-jquery validators. >> > > Without having used tapestry-jquery yet (lack of time, sigh), I'd guess > it's the same as adding Tapestry validations without tapestry-jquery. > > You have a long list of very specific requirements, so maybe the jQuery > validator route will be better suited. > > > >> The reason I chose to use the jQuery validator is for the following >> reasons, >> maybe you could tell me if this is possible using the tapestry version. >> >> 1. We are building a single form with extensive workflow. The form >> essentially remains the same with the exception of validation and user >> role. >> Field validation is completely dynamic from a db and determined based on >> the >> workflows current state. jQuery Validator allows me to validate a field >> based on the class .required. With that being said, I can use a script in >> after render to set all the required classes in the form. I'm not certain >> tapestry would enable me to do this. >> >> 2. Popup form. We have a serious of popup forms that request data. This >> data >> needs to be validated without form submission prior to updating a field >> within the main form. >> >> 3. Dynamic data validation, we need to validate a sum of fields equals >> 100%. >> >> 4. we also need to use an error box to handle some of the dynamic >> validation. >> >> 5. Validate visible fields only. >> >> Like I said, I'm not opposed to the built in version, I'm just not sure >> that >> it's capable of handling all this. If so, could you point me to some >> documentation, it would be greatly appreciated. Thanks Manu. >> >> -- >> View this message in context: http://tapestry.1045711.n5.** >> nabble.com/Tapestry-client-**side-validation-vs-jQuery-** >> Validator-tp5547993p5548091.**html<http://tapestry.1045711.n5.nabble.com/Tapestry-client-side-validation-vs-jQuery-Validator-tp5547993p5548091.html> >> Sent from the Tapestry - User mailing list archive at Nabble.com. >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate > http://www.arsmachina.com.br > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Emmanuel DEMEY Ingénieur Etude et Développement ATOS Worldline +33 (0)6 47 47 42 02 demey.emman...@gmail.com http://emmanueldemey.fr Twitter : @gillespie59
