On Wed, 2004-04-14 at 11:40, Sylvain Wallez wrote:
> Hi all,
>
> A few weeks ago, I generalized validation to every widgets, and not only
> fields. The main visible result of this is that <fd:validation> is now a
> direct child of <fd:field> (or other widget-defining element), and no
> more a child of <fd:datatype>.
>
> Validation as a child of <fd:datatype> is still supported as a legacy
> behaviour, but I would like to remove it to drive people towards the new
> generalized validation. My plan to ease the migration is to raise a
> meaningful exception ("fd:validation has moved") whenever we encounter a
> fd:validation inside a fd:datatype.
Just been looking a bit at this...
For the validation rules associated with datatypes, it is checked that
the validation rule is compatible with the datatype (i.e. can handle the
kind of objects that the datatype represents). Does such a check still
happen? Or will this give errors at runtime?
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
[EMAIL PROTECTED] [EMAIL PROTECTED]
