DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11085>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11085 maxOccurs isn't always enforced Summary: maxOccurs isn't always enforced Product: Xerces2-J Version: 2.0.2 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: XML Schema datatypes AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
