Hi all,
I'm now in a deep preparation for validators rewrite as you might know
from my latest RT, but recently one post on cocoon-users asked about using
xml-schema validation capabilities.
I've taken a short look at the topic and must say that it seems much
easier to reuse xml-schema datatype element to describe data types that your
application is using, and then simply say this request parameter is of that
type, this session one of this type, and voila, ... validation descriptor
structure shouldn't change that much, e.g., still preserving constraint-sets,
and other things, ...
The question is how to implement the actual datatype validation, ...,
as I'm not xml-schema guru so any comments welcome, ..., know that xerces
should have some validation capabilities...
The proposed changes seem to be quite huge, so I'm considering to
leave this topic for only cocoon2.1-dev cause it might bring more bugs and
problems to cocoon2.0 which is almost frozen, ...
what do you think ???
thanx,
martin
--
2CC0 4AF6 92DA 5CBF 5F09 7BCB 6202 7024 6E06 0223
http://mman.dyndns.org/mman.gpg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
