Re: [Soaplite-devel] .Net interoperability and WSDL consuming (was: SOAP Faults and HTTP 1.1 error codes)

[Alceu R. de F. J. <gla...@ya...>]

Hello there Thorsten,

Em 12-05-2011 03:48, Thorsten Schöning escreveu:

> In our software for example we started to use Perl and SOAP::Lite on
> sevrer and client side and didn't care about datatypes, proper
> encoding of data etc. It just worked because SOAP::Lite handled it
> all. Some years late we really have a hard time to support Java, C++,
> C#, publish a WSDL and so on. No we think twice on any change. :-)
>

Now that you have comment that, I'm having some issues to develop a web 
service that can be consumed by a .Net program.

My server and client were working just fine, but then I had to generate 
a WSDL to the .Net client and that was a pain. I used another module to 
help with that and consuming the WSDL with SOAP::Lite client was OK but 
the result was not OK for .Net.

I had to use SOAPUi to validate the WSDL and Eclipse to generate an 
structure that were close of what I was doing to find several small 
issues regarding namespaces.

After I finally got something usable by .Net, the WSDL was not working 
anymore in my SOAP::Lite client.

There is any hope to get things working for both platforms?

Thanks,
Alceu