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

Raymond Feng resolved TUSCANY-1217.
-----------------------------------

    Resolution: Fixed

The issue has been fixed in trunk by setting the system id on the resolved 
InputSource for the import/include.

> Loading nested includes. 
> -------------------------
>
>                 Key: TUSCANY-1217
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1217
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-0.90
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Jean-Sebastien Delfino
>            Priority: Minor
>             Fix For: Java-SCA-Next
>
>
> Lest we forget...
> Currently there is code in WSDLDocumentProcessor.read()  (the two lines with 
> the comment above them).
>             // Read inline schemas
>             Types types = definition.getTypes();
>             if (types != null) {
>                 wsdlDefinition.getInlinedSchemas().setSchemaResolver(new 
> URIResolverImpl());
>                 for (Object ext : types.getExtensibilityElements()) {
>                     if (ext instanceof Schema) {
>                         Element element = ((Schema)ext).getElement();
>                         // TODO: temporary fix to make includes in imported
>                         //       schema work. The XmlSchema library was 
> crashing
>                         //       because the base uri was not set. This 
> doesn't
>                         //       affect imports.
>                         XmlSchemaCollection schemaCollection = 
> wsdlDefinition.getInlinedSchemas();           
>                         
> schemaCollection.setBaseUri(((Schema)ext).getDocumentBaseURI());
>                         wsdlDefinition.getInlinedSchemas().read(element, 
> element.getBaseURI());
>                     }
>                 }
>             }
> Which sets the base dir against which included XSD files are loaded.  However 
> this seems to mean that in the scenario:
> WSDL1 import---> XSD1 inlcude.---> XSD2
>  
> Then XSD2 has to be included relative to the location of WSDL1 which doesn't 
> sound right. 

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to