Yes of course. I saw it only and it striked me as odd, because I used the
inbuilt validator for the first time while playing around with some aspects
of Tap which I never used before.
Most applications will check the email address serverside anyways, for
example to exclude certain domains from whi
Well, you are free to write your own email validator and replace the existing one in
FieldValidatorSource with it.
Cheers,
Uli
Otho schrieb:
Thanks, I misread the regexp. then. But for all "real" email adresses which
are not on the local host or network, the hostname should have at least one
Thanks, I misread the regexp. then. But for all "real" email adresses which
are not on the local host or network, the hostname should have at least one
dot in it, regardless if it's an ip or a host with tld.
2009/1/5 Ulrich Stärk
> Otho schrieb:
>
>> It just occured to me that the email validato
Otho schrieb:
It just occured to me that the email validator used with the @Validate
annotation validates an email-address like 1...@1, which shouldn't be possible
when looking at the source of the Validator.
To my knowledge, 1 is a perfectly legal (although odd) host name and thus qualifies fo
It just occured to me that the email validator used with the @Validate
annotation validates an email-address like 1...@1, which shouldn't be possible
when looking at the source of the Validator.
Setup:
Entity field email annotated with @Validate("required,email")
Beaneditform without
What's also