[ 
https://issues.apache.org/jira/browse/XERCESJ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156637#comment-14156637
 ] 

Michael Glavassevich commented on XERCESJ-1646:
-----------------------------------------------

It's been a long time since I've reviewed that part of the spec but I have 
feeling that this isn't an error. I recall that the validation rules for at 
least some of the facets (enumeration perhaps being one of them) may use the 
base type only for determining the validity of the value.

> Error not reported when the maxLength limit is exceeded in an enumeration
> -------------------------------------------------------------------------
>
>                 Key: XERCESJ-1646
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1646
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema 1.0 Structures
>    Affects Versions: 2.11.0
>            Reporter: Octavian Nadolu
>            Priority: Trivial
>
> If the maxLength limit is exceeded in an enumeration, Xerces engine does not 
> report this error. 
> If I use Saxon engine I get en warning message: 
> "Enumeration value "REQUESTED_CHARGE" is not a valid instance of the type: it 
> contravenes the maxLength facet"
> You can find below a sample schema. I tested on the xml-schema-1.1-dev branch.
> {code:xml}
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>     <xsd:simpleType name="PaymentStatus">
>         <xsd:restriction base="xsd:string">
>             <xsd:maxLength value="15"/>
>             <xsd:enumeration value="AWAIT_PAY_INFO"/>
>             <xsd:enumeration value="AWAIT_AUTH"/>
>             <xsd:enumeration value="REQUESTED_AUTH"/>
>             <xsd:enumeration value="REQUESTED_CHARGE"/>
>             <xsd:enumeration value="PAID"/>
>         </xsd:restriction>
>     </xsd:simpleType> 
> </xsd:schema>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to