Hi Felix,
On Tuesday, June 26, 2012 5:39:28 PM UTC+2, felix hedley wrote:
I know the url is valid - I can browse to it.
I assume you checked that all the imported and included XSD documents inside the WSDL and the Schemas are reachable.
On closer investigation, it appears than none of my services that are served from sites running II6 with ASP>NET option set to 4.0 (as opposed to 2.0) seems to work.
Why would this be, and is there anything I can do about it?
Interesting. Unfortunately we do not have an IIS to test it. You can help us to find the cause of this by looking at the log of the registry (at the console or at a logfile). Maybe you will find an stacktrace there. Then you could place the Membrane Monitor between the registry and the IIS the monitor will intercept the HTTP messages so we can have a look at the HTTP Header fields. To do this do the following:
2.) Create a Proxy to your WSDL file
3.) Get the WSDL using the monitor by replacing the host and port of the WSDL URL with localhost and the port of the Membrane proxy.
4.) Register that URL at the registry.
Now you can see the HTTP traffic in the Monitor and cut and paste it into this group.
--
Thomas