Subjects
• Home
• VOTE Move XML Commons to Xerces
• Commented: (XERCESJ 589) Bug with pattern restriction on long strings
• : Xerces J 2 8 1 Release on Wednesday, September 13th
• : Xerces J 2 9 0 Release on Wednesday, November 22nd
• Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
• Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
• Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
• Some consideration about the xerces DOM implementation
• Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
• Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
• retain exception stack traces
• Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
• Future of NekoHTML
• Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
• DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
• : xml commons external 1 3 04 Release on Wednesday, November 22nd
• Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
• XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
• First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
• : xml commons resolver 1 2 Release on Wednesday, November 22nd
• Typo in RangeToken java Please check
• Validator features
• java lang ClassCastException when adopting Node
• using the org apache xerces impl xs identity package
• Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
• Problem with ref attributes and schema validation
• Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
• Performance problem under load Xerces with Weblogic 9 x
• remove ignored memory allocation
• Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
• Commented: (XERCESJ 977) Null pointer exception during DOM parsing
• Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
• Commented: (XERCESJ 1201) Initial contribution for StAX Event API
• Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
• Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
• Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
• Updated: (XERCESJ 589) Bug with pattern restriction on long strings
• StackOverflow
• xerces Range unnecessarily not garbage collectable if not detached
• Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
• Bug in xs:redefine
• Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
• Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
• Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
• Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
• Google Summer of Code 2007
• Xerces J and XInclude relative path issue
• Assigned: (XERCESJ 206) Stack overflow when using a schema validation
• Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
• Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
• non overriding equals methoda
• Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
• Xerces AS3 port
• Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
• Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
• Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
• Created: (XERCESJ 1124) Nonspecific schema error message
• a bug in xerces
• Updated: (XERCESJ 1201) Initial contribution for StAX Event API
• Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Resolved: (XERCESJ-773) Poor performance when processing schemas with hig

Resolved: (XERCESJ-773) Poor performance when processing schemas with hig

2007-02-23       - By Michael Glavassevich (JIRA)


    [ https://issues.apache.org/jira/browse/XERCESJ-773?page=com.atlassian
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Glavassevich resolved XERCESJ-773.
------------------------------------------

   Resolution: Fixed

I've just committed an improvement to code in SVN which covers a number of
common cases. We now build a representation of large minOccurs/maxOccurs in
constant time and memory (which uses a counter during validation) for element
and wildcard particles when each model group particle in the content model:

* has minOccurs/maxOccurs == 1; or
* contains only one element/wildcard particle with minOccurs/maxOccurs == 1

Handling sequences, choices and nested minOccurs/maxOccurs is somewhat tricker.
 We would need a more general solution than the one implemented for elements
and wildcards to process those gracefully.  I've opened a new JIRA issue [1]
for tracking that.

[1] http://issues.apache.org/jira/browse/XERCESJ-1227

> Poor performance when processing schemas with high values of maxOccurs
> ----------------------------------------------------------------------
>
>                 Key: XERCESJ-773
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-773
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema Structures
>    Affects Versions: 2.5.0
>         Environment: Operating System: Linux
> Platform: PC
>            Reporter: Steve Baker
>         Assigned To: Michael Glavassevich
>
> When validating an instance of an XML order against its schema, the process
took
>  5 minutes 7 seconds and required an increased maximum heap size to run to
> completion.
> The problem was traced to a maxOccurs value of 9999 on an element (the
> OrderLine). Changing this to unbounded reduced the time taked to 1.16 seconds
> and required no increase in the default heap size.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)