W3c Schema validation causes Memory overflow with large maxOccurs
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3142
*** shadow/3142 Thu Aug 16 01:17:05 2001
--- shadow/3142.tmp.14639 Thu Aug 16 05:12:34 2001
***************
*** 44,47 ****
optional,
false);
}
! =====================================================================
--- 44,72 ----
optional,
false);
}
! =====================================================================
!
! ------- Additional Comments From [EMAIL PROTECTED] 2001-08-16 05:12
-------
! I just ran into an StackOverflow Exception. in Method buildSyntaxTree
!
! org.apache.xerces.validators.common.Grammar:
!
! Here it is:
!
! if ((contentSpec.type == XMLContentSpec.CONTENTSPECNODE_CHOICE)
! || (contentSpec.type == XMLContentSpec.CONTENTSPECNODE_SEQ)) {
! //
! // Recurse on both children, and return a binary op node
! // with the two created sub nodes as its children. The node
! // type is the same type as the source.
! //
!
! nodeRet = new CMBinOp( contentSpec.type, buildSyntaxTree
! (leftNode, contentSpec)
! , buildSyntaxTree(rightNode,
! contentSpec));
!
! /* MODIFIED (Jan, 2001) */
!
! } else if (contentSpec.type ==
! XMLContentSpec.CONTENTSPECNODE_ZERO_OR_MORE
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
