hi,
i have a schema that attempts to validate US-state codes
as follows:
<xs:simpleType name="state-code">
<xs:restriction base="xs:string">
<xs:pattern value="\p{Lu}{2}" /> <!-- two upper-case letters -->
</xs:restriction>
</xs:simpleType>
where \p{Lu} is a unicode character class signifying upper case
letters.
with regexp, i get an illegalargumentexception (i.e. it doesn't even
understand the pattern). with oro i get incorrect interpretation of the
pattern
during validation: ValidationException on the valid value "MD"
anyone know what aspects of schema patterns to stay away from
in order to maintain castor validation support?
also, i encountered another small problem running the sourcegenerator
on this:
<xs:simpleType name="state-code">
<xs:restriction base="xs:token">
<xs:pattern value="\p{Lu}{2}" /> <!-- two upper-case letters -->
</xs:restriction>
</xs:simpleType>
notice, the only difference is that i revised the base type to an xs:token.
the error message i get is:
Warning: The W3C datatype 'state-code' is not currently supported
by Castor Source Generator.
any reason why the "token" type is causing problems where the string
type (or possibly even types derived from token) works?
thanks in advance, eitan
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
