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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From [EMAIL PROTECTED] 2002-07-24 08:58 ------- The new build (22 July 2002) does solve the maxOccurs problem - there was a problem with my environment. Thanks for your help I'll close the case. PS I have noted the following output to the console with the new jars. This occurs whether the validation fails or succeeds: .isRegisterNonXS: L isRegisterNonXS: Lu isRegisterNonXS: L isRegisterNonXS: P This doesn't occur with the Test Schema I sent in, but does with the genuine schema I use. A main difference between the test and genuine schemas is that the latter references multiple schemas. *** This bug has been marked as a duplicate of 10474 *** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
