[
https://issues.apache.org/jira/browse/XERCESJ-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878598#action_12878598
]
Michael Glavassevich commented on XERCESJ-1452:
-----------------------------------------------
Added the following messages to XMLSchemaMessages.properties:
cvc-complex-type.2.4.e = cvc-complex-type.2.4.e: ''{0}'' can occur a maximum of
''{2}'' times in the current sequence. This limit was exceeded. At this point
one of ''{1}'' is expected.
cvc-complex-type.2.4.f = cvc-complex-type.2.4.f: ''{0}'' can occur a maximum of
''{1}'' times in the current sequence. This limit was exceeded. No child
element is expected at this point.
cvc-complex-type.2.4.g = cvc-complex-type.2.4.g: Invalid content was found
starting with element ''{0}''. ''{1}'' is expected to occur a minimum of
''{2}'' times in the current sequence. One more instance is required to satisfy
this constraint.
cvc-complex-type.2.4.h = cvc-complex-type.2.4.h: Invalid content was found
starting with element ''{0}''. ''{1}'' is expected to occur a minimum of
''{2}'' times in the current sequence. ''{3}'' more instances are required to
satisfy this constraint.
cvc-complex-type.2.4.i = cvc-complex-type.2.4.i: The content of element ''{0}''
is not complete. ''{1}'' is expected to occur a minimum of ''{2}'' times. One
more instance is required to satisfy this constraint.
cvc-complex-type.2.4.j = cvc-complex-type.2.4.j: The content of element ''{0}''
is not complete. ''{1}'' is expected to occur a minimum of ''{2}'' times.
''{3}'' more instances are required to satisfy this constraint.
> Report better messages for minOccurs/maxOccurs related errors.
> --------------------------------------------------------------
>
> Key: XERCESJ-1452
> URL: https://issues.apache.org/jira/browse/XERCESJ-1452
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.0 Structures
> Affects Versions: 2.9.1
> Reporter: Michael Glavassevich
> Assignee: Michael Glavassevich
> Priority: Minor
> Fix For: 2.10.0
>
>
> Produce more helpful error messages when minOccurs/maxOccurs constraints are
> violated. We're able to do this in cases where we are using a counting DFA.
> The work on this was actually completed last year. Just opening it in JIRA
> now for tracking purposes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
