[
https://issues.apache.org/jira/browse/SYNAPSE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved SYNAPSE-486.
-------------------------------------
Resolution: Fixed
No feedback from reporter. Assuming that the issue is solved by upgrading to
XmlSchema 1.4.3 (done in r748973).
> XSD include treated like XSD import when loading WSDL for proxy service
> -----------------------------------------------------------------------
>
> Key: SYNAPSE-486
> URL: https://issues.apache.org/jira/browse/SYNAPSE-486
> Project: Synapse
> Issue Type: Bug
> Components: Proxy Services
> Affects Versions: 1.2
> Environment: Windows
> Reporter: Joseph Caristi
> Priority: Minor
> Attachments: PartSelectService.wsdl, PartSelectService.xsd,
> synapse_config.xml
>
>
> I am attempting to proxy Axis services using Synapse. The <types> section of
> my WSDL has the following instruction (which works perfectly in Axis):
> <xsd:include schemaLocation="PartSelectService.xsd"/>
> When I point Synapse at the WSDL and XSD, I get the following exception:
> org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in
> collection.
> Namespace: http://www.whisolutions.com/PartSelectService/2008-10-07
> This is the only namespace for my service. Both the WSDL and XSD have the
> same namespace. This is why I am using an xsd:include rather than an
> xsd:import. This all worked before I extracted my types into a separate XSD
> file.
> Complete details available in Synapse user forum:
> http://www.nabble.com/XMLSchemaException-when-including-XSD-in-WSDL-td20671355.html#a20786238
--
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]
