tags:

views:

221

answers:

1

I'm trying to use NeoLoad to generate and execute SOAP requests and upon supplying the WSDL, it doesn't seem to like the imports that they are referring to.

I'm thinking I would need to flatten the WSDL generated by the WCF service.

Are there any techniques I could use to flatten it?

I've been reading:

http://blogs.msdn.com/dotnetinterop/archive/2008/09/23/flatten-your-wsdl-with-this-custom-servicehost-for-wcf.aspx

http://blogs.thinktecture.com/cweyer/archive/2007/05/10/414840.aspx

Would this be something I should be trying out?

+1  A: 

Yes, some clients have trouble with the (standards-compliant) way that Microsoft has implemented the WSDL and XSD.

Those two articles you mention are great starting points - they show how you can get your WCF service to render out a flattened WSDL (which includes the XSD inside it).

The same goes for WCF Extras on Codeplex, which also does a few more things in addition (most notably exporting the XML comments from your C# or VB.NET code into the WSDL). Highly recommended.

marc_s
No, as their code shows - that is not required. There are several ways to do this.
marc_s
It still appears that my <wsdl:types/> is empty. Hmm I think this is why it could not recognize it.
Floetic
Which one of those tools are you using now? I've tried the WCF Extras and they did indeed work for me.
marc_s
You do have your data classes marked with `[DataContract]` and your fields you want to have in the message with `[DataMember]`, I presume...
marc_s
Yes I do have them marked that way. I'm using a tool called NeoLoad http://www.neotys.com/index.php?lang=en and it doesn't seem to like the WSDL I'm generating.
Floetic
java.lang.RuntimeException: Can't resolve method parameter:Part: name=parameterselementName={http://something/something}UpdateSomething
Floetic
http://winterdom.com/2006/10/inlinexsdinwsdlwithwcf is maybe something I will need to work on.
Floetic