SoapBinding and Soap12Binding with 0.7 pre1

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use wsdl2objc on http://ranking.iaelu.net/RankingProxy.asmx?wsdl
2. check the code for the SoapBinding in RankingProxy.m

What is the expected output?
For the SoapBinding, the header of the request is set to application/soap+xml
For the SoapBinding, the header response is checked against application/soap+xml

What do you see instead?
For the SoapBinding, the header of the request should be set to text/xml
For the SoapBinding, the header response should be checked against text/xml

What version of the product are you using? On what operating system?
0.7 pre1, on MacOSX 10.6.3

Please provide any additional information below.
I've been checking the code for wsdl2objc, and the template for the binding is 
looking like it 
should be ok, but the generated code is still looking like the SoapBinding is a 
Soap12Binding.
Sorry if it's not clear. Just let me know if you don't understand, i'll try to 
explain it as well as I 
can.
That's a great project, but maybe it's a bit hard to use it. I think it needs a 
wrapper that can hide 
the complexity and provide a much easier interface for users.
Anyway, good job, keep going :)

cheers!

Original issue reported on code.google.com by guillaum...@gmail.com on 12 May 2010 at 11:43

[GoogleCodeExporter]

This problem is known (at least to me :) ) in that wsdl2objc hard-codes the 
type based on the LATEST available 
SOAP version.
Here's the way it works:
- If there's only SOAP 1.1, it uses 1.1 and applies text/xml
- If there's only SOAP 1.2, it uses 1.2 and applies application/soap+xml
- If both SOAP 1.1 and 1.2 exist, it uses 1.2 and applies application/soap+xml

So in your situation, just use the 1.2 bindings (Soap12Binding) and disregard 
the 1.1 bindings and methods.

Original comment by hasse...@gmail.com on 13 May 2010 at 7:05

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision r177.

Original comment by hasse...@gmail.com on 9 Sep 2010 at 1:00

• Changed state: Fixed

[GoogleCodeExporter]

Should be fixed by Stephane's patch, which I added in revision 177.
Please verify.

Original comment by hasse...@gmail.com on 9 Sep 2010 at 1:00