[
https://issues.apache.org/jira/browse/ODE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489839
]
Alex Boisvert commented on ODE-111:
-----------------------------------
Also worth saying is the path resolution does not use or interpret the
targetNamespace as a base URL.
The base URL for all imports and includes is the location of the context
document.
So if I have the following deployment package structure:
foo/bar/baz.wsdl
<wsdl:types>
<xs:schema targetNamespace="uri:thisIsNeverUsedAsAURL">
<xs:include schemaLocation="../../mySchemaTypes.xsd"/>
</xs:schema>
</wsdl:types>
then it is expected that mySchemaTypes.xsd is available at the root of the
deployment package.
> Support <xsd:include> with relative schemaLocation
> --------------------------------------------------
>
> Key: ODE-111
> URL: https://issues.apache.org/jira/browse/ODE-111
> Project: Ode
> Issue Type: Improvement
> Components: BPEL Compilation/Parsing
> Reporter: Alex Boisvert
> Assigned To: Alex Boisvert
> Fix For: 1.0-incubating
>
>
> Improve the BPEL compiler to support <xsd:include> with relative
> schemaLocation, such as:
> <wsdl:types>
> <xs:schema
> targetNamespace="http://www.intalio.com/training/orderManagement_20061017";>
> <xs:include schemaLocation="../../OrderManagement.xsd"/>
> </xs:schema>
> </wsdl:types>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
