[jira] Resolved: (TUSCANY-3153) imported XSDefinition should be set with XmlSchema as well

["Raymond Feng (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raymond Feng resolved TUSCANY-3153.
-----------------------------------

    Resolution: Fixed

Fixed in 2.x, 1.x and 1.5.1 streams

> imported XSDefinition should be set with XmlSchema as well
> ----------------------------------------------------------
>
>                 Key: TUSCANY-3153
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3153
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>            Reporter: Scott Kurz
>            Assignee: Raymond Feng
>            Priority: Minor
>
> When A.xsd imports B.xsd, with different TNS for A and B, the loadOnDemand() of A will cause an XmlSchema for B to be stored in the schemaCollection, but we never do setSchema(XmlSchema) for the XSDefinition corresponding to B.    Later, .. if we try to resolve B's XSDefinition, we will not do another read(), since we detect that we already have loaded B.xsd (since the schemaCollection already has an entry for the TNS of B).   However, the getSchema() returns null for B's XSDefinition.    
> Not sure I understand this well enough to suggest the best way to fix it.   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.