We do plan to implement Validator (at least some cases), but right now it's probably best to implement any client-side validation yourself.
Note that validators coming from server responses show the expected error messages. So if you have validators in your .ds.xml file, there's nothing you need to do - validation just works - the purpose of implementing client-side validation would be for optimization reasons.
Thanks for your reply. I need a dynamic MaskValidator, dynamic because the mask itself is taken from a property table in the DB and can be changed by the (admin) user. This makes it difficult (impossible?) to implement in the .ds.xml only. I will do it myself as you suggest.
Not impossible or even difficult - look at this sample and the others in the folder. It's easy to have validators call Java logic, dynamic data is not an issue.
Comment