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 05:12:34 2001
--- shadow/3142.tmp.14941 Thu Aug 16 06:50:05 2001
***************
*** 2,15 ****
| W3c Schema validation causes Memory overflow with large maxOccurs |
+----------------------------------------------------------------------------+
| Bug #: 3142 Product: Xerces-J |
! | Status: NEW Version: 1.4.2 |
! | Resolution: Platform: PC |
| Severity: Normal OS/Version: Windows NT/2K |
| Priority: Other Component: SAX |
+----------------------------------------------------------------------------+
| Assigned To: [EMAIL PROTECTED] |
| Reported By: [EMAIL PROTECTED] |
- | CC list: Cc: |
+----------------------------------------------------------------------------+
| URL: |
+============================================================================+
--- 2,14 ----
| W3c Schema validation causes Memory overflow with large maxOccurs |
+----------------------------------------------------------------------------+
| Bug #: 3142 Product: Xerces-J |
! | Status: RESOLVED Version: 1.4.2 |
! | Resolution: WONTFIX Platform: PC |
| Severity: Normal OS/Version: Windows NT/2K |
| Priority: Other Component: SAX |
+----------------------------------------------------------------------------+
| Assigned To: [EMAIL PROTECTED] |
| Reported By: [EMAIL PROTECTED] |
+----------------------------------------------------------------------------+
| URL: |
+============================================================================+
***************
*** 70,72 ****
--- 69,89 ----
} else if (contentSpec.type ==
XMLContentSpec.CONTENTSPECNODE_ZERO_OR_MORE
+
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-08-16 06:50 -------
+ Hi Volkmar,
+
+ This is a known problem/limitation of Xerces. maxOccurs=999999 results in a
+ sequence of 999999 (possibly optional) elements. So definitely you'll get
+ OutOfMemory or StackOverflow exception.
+
+ We don't plan to fix/improve this in Xerces1. In fact, we didn't see many
+ requirements for large occurrence value support. In most cases,
+ maxOccurs=unbounded would be a better choice.
+
+ But we are considering supporting such case in Xerces2. It's still in design
+ phase, so we are open for any suggestions.
+
+ Cheers,
+ Sandy Gao
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
