synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] Commented: (SYNAPSE-486) XSD include treated like XSD import when loading WSDL for proxy service
Date Sat, 20 Dec 2008 23:50:44 GMT


Andreas Veithen commented on SYNAPSE-486:

This issue looks like WSCOMMONS-377. Can you replace the XmlSchema JAR bundled with Synapse
by version 1.4.3 downloaded from [1] and retest?


> XSD include treated like XSD import when loading WSDL for proxy service
> -----------------------------------------------------------------------
>                 Key: SYNAPSE-486
>                 URL:
>             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:
> Schema name conflict in collection.
> Namespace:
> 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:

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:
For additional commands, e-mail:

View raw message