This seems like a bug we need to fix.. but I guess there is a workaround
for you for now..
Could you raise this on the JIRA?
asankha
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. Is Synapse treating this like an import? This all worked
before I extracted my types into a separate XSD file.
Here is my WSDL:
http://www.nabble.com/file/p20671355/PartSelectService.wsdl
PartSelectService.wsdl
Here is my XSD:
http://www.nabble.com/file/p20671355/PartSelectService.xsd
PartSelectService.xsd
Here is my Synapse configuration:
http://www.nabble.com/file/p20671355/synapse_config.xml synapse_config.xml
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
