Adding a web service client with 'Execute by default' = Yes, interrupts the normal page execution. I'm trying this web service:
http://bible.sumerano.com/bible.asmx (wsdl: http://bible.sumerano.com/bible.asmx?WSDL)
Call the method 'GetBooks' without parameters.
There are some compatibility issues beetwewn SOAP::Lite and .NET Web Services.
I'm making a new WSClient (something like WebGUI::Asset::Wobject::WSClientSharp) for .NET.
Can you elaborate on what incompatibilities you have found?
You can see the SOAP::Lite documentation at:http://search.cpan.org/~mkutter/SOAP-Lite-0.710.08/lib/OldDocs/SOAP/Lite.pm#INTEROPERABILITY
and this MSDN article:http://msdn.microsoft.com/en-us/library/ms995764.aspx
Fabio.
Since the .NET WS Client needs to know it is talking to a .NET server, I'm moving this to an RFE to add a flag to the client that the server is .NET. If you get your Sharp version finished, we could merge that back into the WSClient if you wanted.
Ok. I'll try to develop it with the flag, without duplicating the WSClient.
Bye.
This is the same bug as http://www.webgui.org/bugs/tracker/wsc-wobject#hk0giovZ2IqCehKNDDBRaw
