Sorry, I would have to disagree on that. By your logic then we should also have IntegerTextField, CurrencyTextField, DecimalTextField, RequiredEmailTextField, RequiredIntegerTextField, RequiredCurrencyTextField and so on. This would soon become a real mess and very complex to use. The validator and convertor mechanisms within Wicket are so powerful that you can do pretty much anything you ever need to do while keeping the number of core classes very small and focused.
Now that the new EmailAddressPatternValidator has been added what could be easier than:
new TextField("emailAddress", someModel).add(new EmailAddressPatternValidator());
Regards,
Chris
>
>
> I still think we should have a proper emailAddressField
> component in the core distrubution as a convenience component
> similar to RequiredTextField.
> Les
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from
> real users. Discover which products truly live up to the
> hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396> &op=click
>
> _______________________________________________
>
> Wicket-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/w> icket-user
>
>
