[jboss-jira] [JBoss JIRA] Commented: (JBCOMMON-43) JBossEntityResolver: xsd:redefine resolution

[Alexey Loubyansky (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCOMMON-43?page=comments#action_12403126 ] 
            
Alexey Loubyansky commented on JBCOMMON-43:
-------------------------------------------

The fix has been committed with a testcase. I want to bring to attention that there is a possible backwards incompatibility in behavior (which affects any case when resolveEntity is called) in that if the schema location registered in the resolver is different from the one in the XML's schemaLocation attribute with the purpose of override. In this case, the schemaLocation from the XML file will be used. And at the moment w/o falling back to the registered one if the one in the XML occured to be invalid.

> JBossEntityResolver: xsd:redefine resolution
> --------------------------------------------
>
>                 Key: JBCOMMON-43
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-43
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core
>    Affects Versions: 2.2.3.GA
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: 2.2.4.GA
>
>
> What happens is the parser resolving xsd:redefine passes the namespace of the redefining schema as publicId and the schema location of the redefined schema as systemId. If the redefining schema's namespace has already been mapped to a schema location of the redefining schema then the schema location argument is ignored and the redefining schema is returned instead of the redefined schema.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira