[
https://issues.apache.org/jira/browse/XERCESJ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519183
]
Michael Glavassevich commented on XERCESJ-1227:
-----------------------------------------------
Georg, doesn't seem like you noticed what this bug report is for. It's a catch
all for a number of more complex / less common cases involving
minOccurs/maxOccurs. An improvement for large minOccurs/maxOccurs on elements
and wildcards has already been implemented and will be in the next release.
That would seem to cover the fragment of your schema which you've posted here.
> Poor performance / OutOfMemoryError for sequences, choices and nested with
> large minOccurs/maxOccurs
> ----------------------------------------------------------------------------------------------------
>
> Key: XERCESJ-1227
> URL: https://issues.apache.org/jira/browse/XERCESJ-1227
> Project: Xerces2-J
> Issue Type: Bug
> Components: XML Schema Structures
> Affects Versions: 2.9.0
> Reporter: Michael Glavassevich
> Priority: Minor
>
> We now handle large minOccurs/maxOccurs on element/wildcard particles more
> gracefully by creating a compact representation in the DFA and using counters
> to check the occurence constraints, however we will still fully expand the
> content model for minOccurs/maxOccurs on sequences and choices which could
> still lead to an OutOfMemoryError or very poor performance (i.e. could still
> take several minutes to build the DFA). Sequences, choices and nested
> minOccurs/maxOccurs are somewhat tricker to handle. We would need a more
> general solution than the one implemented for elements and wildcards to
> improve those.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
