[ 
https://issues.apache.org/jira/browse/XERCESJ-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500095#comment-13500095
 ] 

Radu Coravu edited comment on XERCESJ-1595 at 11/19/12 1:15 PM:
----------------------------------------------------------------

So basically the fix should be in two places:

1) The methods:

org.apache.xerces.impl.xs.XSDDescription.equals(Object)
and
org.apache.xerces.impl.xs.XSDDescription.hashCode()

should also look at the literal system ID if the target namespace is NULL

2) The method:

org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(short, String, 
QName, QName, XMLAttributes)

should also set a literal system ID to the 
"org.apache.xerces.impl.xs.XMLSchemaValidator.fXSDDescription" before passing 
it through the grammar pool.
                
      was (Author: radu_coravu):
    So basically the fix should be in two places:

1) The methods:

org.apache.xerces.impl.xs.XSDDescription.equals(Object)
and
org.apache.xerces.impl.xs.XSDDescription.hashCode()

should also look at the literal system ID if the target namespace is NULL

2) The method:

org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(short, String, 
QName, QName, XMLAttributes)

should also set a literal system ID to the 
"org.apache.xerces.impl.xs.XMLSchemaValidatorXerces.fXSDDescription" before 
passing it through the grammar pool.
                  
> Xerces grammar pool not working with no namespace XSDs
> ------------------------------------------------------
>
>                 Key: XERCESJ-1595
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1595
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XNI
>    Affects Versions: 2.11.0
>            Reporter: Eric Sirois
>             Fix For: 2.11.0
>
>
> When loading XSDs with no namespace into the Xerces grammar pool, it assumes 
> every XSD with no namespace to be the same XSD doc.  In our case, when trying 
> to validate DITA documents, there could be a number of different types of 
> documents involved, for example map, topic, task and concepts.
> To get around the issue we need to ignore XSDs when loading the grammar pool. 
>  This affects the time needed to produce/transform documentation 
> significantly.
> If a namespace is available for the XSD, the grammar cache should use that. 
> If the there is no namespace available, then it should use the system ID of 
> the schema.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to