Ben Gunter wrote:

> Generally, when validating email addresses, you either want to add
> @DontAutoload to the TypeConverter class or put it in a package that is not
> considered for autoloading. Then, for each email address field, you'd use
> @Validate(converter=MyEmailTypeConverter.class) to specify the type
> converter for that field.

Ah right, I thought there must be a trick to it - thanks.

We have custom date, date/time and integer converters as well, to work 
round bugs in Stripes ones, and we are specifying them all with 
'converter='.  Should we tag them with @DontAutoload as well?

To be honest, type converters are one of the less satisfactory areas of 
Stripes - not the principle, just the implementations.

-- 
Alan Burlison
--

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users

Reply via email to