Subject:WSDL Misbehaving Author:Nick Locke Date:14 Nov 2007 08:00 AM
I have a WSDL structure which I have created using Stylus Studio. It has the "Service" in one WSDL file and the "Messages" in another. The "Messages" file references a number of XSDs.
I am trying to use the Web Service Call Composer and, although it "sees" the three Operations, I can't get any further.
I have run the WSDL through the validator at www.xmethods.com and that does not find any errors. I can also generate .NET code using Microsoft's WSDL.EXE (which is usually very fussy).
I have attached a screen-shot from Stylus Studio. It is worth mentioning that SOAP Sonar also shows similar behaviour - in that tool, I can see the XML Elements within the SOAP Header, but then just get a single tag called "Body" rather than the XML elements that I would expect.
Subject:WSDL Misbehaving Author:Nick Locke Date:14 Nov 2007 12:13 PM
> This is caused by a restriction
> in the Stylus Studio WSDL processor
> that doesn't support wsdl:import.
Ivan, thanks for the prompt and helpful response. Does this just mean that I cannot split the WSDL Service and the WSDL Messages into separate files, or does it go further and mean that I can't import the XSD files either?
I guess I could live with combining the Service and Message WSDL files, but I need to keep the XSDs separate.