Importing wsdl into webmethods that has XSD imports in the definition

I’m the provider for my cient. I’ve a WSDL provided by the client. This wsdl contains all the imports to the XSD’s (It does not expand the XSDs).

I’m on webMethods 8.0 server on UNIX.

Also, what version of WSDL (1.0 or 2.0) does webmethods 8.0 support/generate?


<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:tns="" xmlns:wsdl= xmlns:soap="" xmlns:xsd="XML Schema" xmlns:osData="" xmlns:osOrderRequest="" targetNamespace="">
<wsdl:documentation>Ordering Service</wsdl:documentation>

<xsd:import namespace="" schemaLocation="OrderRequest.xsd[FONT=Arial][SIZE=2][COLOR=#0000ff][FONT=Arial][SIZE=2][COLOR=#0000ff]"/> …

Question: Where should I keep this wsdl and xsd on my server for the succesful import of the wsdl?



As the provider of the web service it is you that should be defining the WSDL, not the client.

Review the wM-supplied documentation for creating a WSD, doc types, etc. in IS from a WSDL. The steps are pretty clear.

What you said is absolutely true. That’s what the process is and I suggested that. but I don’t have control on that except importing the WSDL provided by client as it comes from government and has some scurity issues.

So, Just want to know if I can import at all.

When you import a WSDL, it will create the document types and schemas from the schemas that are either defined inline in the WSDL or imported from external xsd files. Those doc types are what you will use to implement a flow or java service that provides a service with the interface described in the WSDL.

Yes you can import WSDL provided by your end provider client…Are you getting any errors with loading WS-Security headers or some thing?

As Mark stated above the way it will work and be used in WSD consumer mapping interface perspective: