Hi Evanthika,
I see that your wsdl fully qualifies the location of the schema import
location. I am using Axis2 to host the service. When the service is
built and deployed, the schemaLocation attribute is set to locate the
schema relative to the service. So, Axis2 produces something along the
following:
<xs:import namespace="..." schemaLocation="ServiceName?xsd0=xsd0.xsd"/>
As a result Synapse will try to resolve to the filesystem, relative to
the base of the repository. So, while this works in your case, it may
not work in other cases where the schemaLocation is defined as above.
Thanks,
Alejandro
Evanthika Amarasiri wrote:
Hi Alejandro,
I was able to create a proxy service with the publishWSDL uri given as
an http url. Also I have an XSD import within this WSDL where the xsd
is hosted at a remote server.
The location of the WSDL file -
http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl (As specified
in the below configuration)
The location of the XSD file -
http://ww2.wso2.org/~evanthika/wsdl/import_schema.xsd (Refered in the
import_schema.wsdl file)
Below is the configuration that I tried.
<proxy name="TestProxyService" transports="https http"
startOnLoad="true">
<target>
<inSequence>
<send>
<endpoint>
<address
uri="http://localhost:9000/soap/SimpleStockQuoteService"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<publishWSDL
uri="http://ww2.wso2.org/~evanthika/wsdl/import_schema.wsdl"/>
</proxy>
I was able to start the above configuration successfully. Can you
check your WSDL, XSD files and the configuration against mine and see
whether you have properly created the files?
Thanks,
Evanthika
Asankha C. Perera wrote:
Alejandro
Ah, I tried that once and it failed. I gave it a try again and took
a closer look at the logs. It looks like it cant resolve imported
schema references.
This probably is a bug.. Evanthika can you check this and make that a
test case for the releases?
asankha
