The following issue has been updated:
Updater: Serge Knystautas (mailto:[EMAIL PROTECTED])
Date: Mon, 12 Apr 2004 2:23 PM
Changes:
Attachment changed from TestSchema.xsd
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XERCERJ-396?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCERJ-396
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCERJ-396
Summary: maxOccurs isn't always enforced
Type: Bug
Status: Resolved
Resolution: DUPLICATE
Project: Xerces2-J
Assignee: Xerces-J Developers Mailing List
Reporter: Paul
Created: Tue, 23 Jul 2002 2:20 PM
Updated: Mon, 12 Apr 2004 2:23 PM
Environment: Operating System: Windows NT/2K
Platform: PC
Description:
maxOccurs is often not enforced correctly.
The following occurs
(OK = maxOccurs enforced correctly
FAIL = maxOccurs isn't enforced - ie more than expected elements
can be added to an XML instance)
1. minOccurs=0, maxOccurs=1 - OK
2. minOccurs=0, maxOccurs=2,3,4 - FAIL
3. minOccurs=1, maxOccurs=2 - OK
4. minOccurs=1, maxOccurs=3,4,5 - FAIL
5. minOccurs=2, maxOccurs=3 - OK
6. minOccurs=2, maxOccurs=4,5,6 - FAIL
ie it appears that a gap of 1 between minOccurs and maxOccurs is OK,
but any more gap and the validation doesn't work
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
