Hi,

I've got a proxy setup in Synapse for a web service that has a wsdl with imported xsd schema files. That is, the WSDL imports all its schema definitions instead of having them inline in the WSDL document.Synapse is running within Axis2 using the Synapse MAR file.

When I use the publishWSDL tag in my proxy definition in synapse.xml, it cannot publish the WSDL due to not being able to find the included XSD files. Instead of looking at the http location or the local file path for the file, it always looks under the work/Catalina folder of my Tomcat, and hence never finds it.

The only way around this, for our production setup is to inline the XSDs into the WSDL, which works but is a hassle, especially when running 6 different web services all sharing schema libraries.

Is there any way around this instead of having to either (a) inline schemas into the WSDL or (b) contain absolute paths to the schema files in the WSDL (which is bad because the paths are completely different between development machines, the development server and the test/production server setup.

cheers,
Anthony

--

Anthony
------------------------------------- Anthony Bull
Senior Developer
Black Coffee Software Ltd
PO Box 10-192 The Terrace
Wellington, New Zealand

[EMAIL PROTECTED]
Ph  +64 4 472 8818
Fax +64 4 472 8811
------------------------------------- www.bcsoft.co.nz --------------------------------------------------------------- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. ---------------------------------------------------------------

Reply via email to