cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: [cforms] Moving <validation> out of <datatype>
Date Wed, 14 Apr 2004 10:40:09 GMT
Antonio Gallardo wrote:

>Sylvain Wallez dijo:
>>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.
>+1 - Why care about legacy, when the block is still unstable? :-D

Because many users already use that nice unstable blocks ;-)

And because I prefer Cocoon to automatically direct people in the right 
direction than having to answer tons of questions related to "why does 
validation not occur?". Programmers are lazy ;-P


Sylvain Wallez                                  Anyware Technologies 
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }

View raw message