Thank you, Hugo for the help. I was also checking the T5 documentation and found that default (recommended) way for email validation is roll-your-own validation based on the regular expressions that are stored inside properties. This is really, really innovative and unusual way to do that for me (although I'm a T4 user) because:
1. Properties/Resources bundle are used for externationalization of the strings/resources and not for defining validation rules, storing regular expression in properties is abnormal way to achieve validation, as a new T5 user I will never look to the properties file for validation rules. 2. Email validation rules are the same for all languages therefore using DRY we shall put it only in one resource bundle, however inconsistent properties in resource bundles is a bad sign and with some validation rules it could even lead to the broken build. 3. Although I think having different validation rules for different languages is a very good idea and might be useful but IMHO you aren't gonna need it in the most of the cases. I think we need a specific email validator that can be optionally parametrized by the key of the error message. Renat On 11/02/2008, Hugo Palma <[EMAIL PROTECTED]> wrote: > > This thread should help you: > > http://www.mail-archive.com/users@tapestry.apache.org/msg20213.html > > Renat Zubairov wrote: > > Hello T5 users, > > What is the default approach of handling email validation inside the > > form/beanEditForm? > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Best regards, Renat Zubairov
