Hello, I've reposted this message because I did not get a reply stating whether the large maxOccurs issue will ever be resolved. One of the limitations stated in the schema programming page for Xerces C++ states ... <http://xml.apache.org/xerces-c/schema.html> * Due to the way in which the parser constructs content models for elements with complex content, specifying large values for the minOccurs or maxOccurs attributes may cause a stack overflow or very poor performance in the parser. Large values for minOccurs should be avoided, and unbounded should be used instead of a large value for maxOccurs. When validating an XML file with a schema file that contains four instances of complex content items where maxOccurs="999", the validation completes in 32875 milliseconds. If I change the maxOccurs="999" instances to maxOccurs="unbounded", the validation completes in 543 milliseconds. Unfortunately, my application requires the upper bound check of "999". Is there an attempt being made to resolve this limitation in xerces other than use of maxOccurs="unbounded"?
Thanks, M. Scott Gordon ADSS Software Engineer BAE Systems Mission Solutions Inc. [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
