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 ------- Additional Comments From [EMAIL PROTECTED] 2002-07-23 16:25 ------- I've created a cut-down TestSchema and an XML instance. This reproduces the maxOccurs bug of the Schemas I'm using. The XML instance has 4 elements of a type which should be constrained to a maximum of 3 elements using the Test Schema (the second version attached - 16:14). Using the latest Xerces-J jars (22-Jul-2002), on NT, using JDK1.3.1, the validation does NOT produce an error. The tests mentioned below (based on different values of minOccurs and maxOccurs) produce the same results using the Test Schema. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
