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.
-Ben
On Mon, Aug 10, 2009 at 2:21 PM, Alan Burlison <[email protected]>wrote:
> I want to add some additional checking to email addresses, so I've
> defined my own TypeConverter:
>
> public class MyEmailTypeConverter extends EmailTypeConverter { ... }
>
> And it is being called to validate *every* string field, even those that
> don't have any @validate annotation at all. Naturally this completely
> breaks my entire application.
>
> I've extended other converters in the past, such as the date & time
> ones, and even the integer one and never had any problems.
>
> I'm assuming the reason Stripes has collapsed in a heap is because it
> selects the type converter based on the return type and parameters of
> the various convert methods it finds, and in this case email addresses
> are just strings, so it is using my email converter instead of the
> default string converter - although I can't understand why the same
> brokenness doesn't affect the standard email converter.
>
> I haven't found any other instances of this problem being reported and
> I'm finding it difficult to understand how such a big bug (if it is one)
> could have gone unnoticed?
>
> --
> 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
