You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org> on 2009/11/24 04:24:40 UTC
[jira] Created: (XERCESJ-1406) Performance:
XMLSchemaValidator.findSchemaGrammar() called too often.
Performance: XMLSchemaValidator.findSchemaGrammar() called too often.
---------------------------------------------------------------------
Key: XERCESJ-1406
URL: https://issues.apache.org/jira/browse/XERCESJ-1406
Project: Xerces2-J
Issue Type: Improvement
Components: XML Schema 1.0 Structures
Affects Versions: 2.9.1
Reporter: Michael Glavassevich
On every startElement() call we attempt to look-up a SchemaGrammar which is usually never read. In the best case it's already in the XMLGrammarPool, but when we're processing a local elements with no namespace we're likely to end up calling the EntityResolver over and over again (even when none is register we always go through XMLEntityManager.resolveEntity()), attempting to load an empty XMLInputSource with the schema loader and after all that returning null back from the method. That's a lot of wasted time.
--
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@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Assigned: (XERCESJ-1406) Performance:
XMLSchemaValidator.findSchemaGrammar() called too often.
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich reassigned XERCESJ-1406:
---------------------------------------------
Assignee: Michael Glavassevich
> Performance: XMLSchemaValidator.findSchemaGrammar() called too often.
> ---------------------------------------------------------------------
>
> Key: XERCESJ-1406
> URL: https://issues.apache.org/jira/browse/XERCESJ-1406
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.0 Structures
> Affects Versions: 2.9.1
> Reporter: Michael Glavassevich
> Assignee: Michael Glavassevich
>
> On every startElement() call we attempt to look-up a SchemaGrammar which is usually never read. In the best case it's already in the XMLGrammarPool, but when we're processing a local elements with no namespace we're likely to end up calling the EntityResolver over and over again (even when none is register we always go through XMLEntityManager.resolveEntity()), attempting to load an empty XMLInputSource with the schema loader and after all that returning null back from the method. That's a lot of wasted time.
--
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@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Resolved: (XERCESJ-1406) Performance:
XMLSchemaValidator.findSchemaGrammar() called too often.
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich resolved XERCESJ-1406.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.10.0
Implemented in SVN rev 883581.
> Performance: XMLSchemaValidator.findSchemaGrammar() called too often.
> ---------------------------------------------------------------------
>
> Key: XERCESJ-1406
> URL: https://issues.apache.org/jira/browse/XERCESJ-1406
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.0 Structures
> Affects Versions: 2.9.1
> Reporter: Michael Glavassevich
> Assignee: Michael Glavassevich
> Fix For: 2.10.0
>
>
> On every startElement() call we attempt to look-up a SchemaGrammar which is usually never read. In the best case it's already in the XMLGrammarPool, but when we're processing local elements with no namespace we're likely to end up calling the EntityResolver over and over again (even when none is registered we always go through XMLEntityManager.resolveEntity()), attempting to load an empty XMLInputSource with the schema loader and after all that returning null back from the method. That's a lot of wasted time.
--
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@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
[jira] Updated: (XERCESJ-1406) Performance:
XMLSchemaValidator.findSchemaGrammar() called too often.
Posted by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org>.
[ https://issues.apache.org/jira/browse/XERCESJ-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Glavassevich updated XERCESJ-1406:
------------------------------------------
Description: On every startElement() call we attempt to look-up a SchemaGrammar which is usually never read. In the best case it's already in the XMLGrammarPool, but when we're processing local elements with no namespace we're likely to end up calling the EntityResolver over and over again (even when none is registered we always go through XMLEntityManager.resolveEntity()), attempting to load an empty XMLInputSource with the schema loader and after all that returning null back from the method. That's a lot of wasted time. (was: On every startElement() call we attempt to look-up a SchemaGrammar which is usually never read. In the best case it's already in the XMLGrammarPool, but when we're processing a local elements with no namespace we're likely to end up calling the EntityResolver over and over again (even when none is register we always go through XMLEntityManager.resolveEntity()), attempting to load an empty XMLInputSource with the schema loader and after all that returning null back from the method. That's a lot of wasted time.)
> Performance: XMLSchemaValidator.findSchemaGrammar() called too often.
> ---------------------------------------------------------------------
>
> Key: XERCESJ-1406
> URL: https://issues.apache.org/jira/browse/XERCESJ-1406
> Project: Xerces2-J
> Issue Type: Improvement
> Components: XML Schema 1.0 Structures
> Affects Versions: 2.9.1
> Reporter: Michael Glavassevich
> Assignee: Michael Glavassevich
>
> On every startElement() call we attempt to look-up a SchemaGrammar which is usually never read. In the best case it's already in the XMLGrammarPool, but when we're processing local elements with no namespace we're likely to end up calling the EntityResolver over and over again (even when none is registered we always go through XMLEntityManager.resolveEntity()), attempting to load an empty XMLInputSource with the schema loader and after all that returning null back from the method. That's a lot of wasted time.
--
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@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org