[
https://issues.apache.org/jira/browse/XERCESJ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Glavassevich updated XERCESJ-1227:
------------------------------------------
Description:
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.
With the introduction of XML Schema 1.1 support we would also need to consider
how to improve this for the enhanced xs:all model groups.
was: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.
> 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 1.0 Structures, XML Schema 1.1 Structures
> Affects Versions: 2.9.0
> Reporter: Michael Glavassevich
> Priority: Minor
> Labels: gsoc, gsoc2014, mentor
>
> 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.
> With the introduction of XML Schema 1.1 support we would also need to
> consider how to improve this for the enhanced xs:all model groups.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
