function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
sfdctrrsfdctrr 

Apex generation Failed: Una​ble to find soap 1.1 address

Hi,

         I'm working on integration and my client has given me the WSDL file and it uses soap12 service , it doesn't have soap11 but when i try to generate apex classes from WSDL it throws the above exception(Apex generation Failed: Una​ble to find soap 1.1 address).

 

          I have gone through the following link but didn't find solution to my problem.

http://boards.developerforce.com/t5/General-Development/Help-needed-Unable-to-find-soap-1-1-address/m-p/311069/highlight/false#M57988

 

 

Any help appreciated.

 

Thanks,

Rajeshwar.

_Prasu__Prasu_

Apex class can be generated from the Soap 1.1 services, so as your WSDL contains only soap 1.2 services its failing. You will need WSDL which uses soap 1.1 service.

sfdctrrsfdctrr

THx for your reply.

My client has given me the only SOAP 1.2 service  WSDL and client doesn't have SOAP 1.1 service WSDL, what should i do now. what is the alternate approch or any suggestions appreciated.

 

Thanks.

 

URVASHIURVASHI

Hey sfdctrr did u find a solution for this?

i m too facing the same prblm.

pls help.

 

Thanks.

 

_Prasu__Prasu_

Check if this helps: http://stackoverflow.com/questions/7189134/wcf-basichttpbinding-where-can-i-find-soap1-1-in-wsdl

 

Else you will need to manually create the Soap request and parse the Soap response using XMLDom class.

sunny522sunny522
Hi sfdctrr,
      This error will occur when we use soap12 binding in wsdl file like the one below
<wsdl:binding name="Service1Soap12" type="tns:Service1Soap">...</wsdl:binding>

If your wsdl have 2 bindings like below

<wsdl:binding name="Service1Soap" type="tns:Service1Soap">...</wsdl:binding>
<wsdl:binding name="Service1Soap12" type="tns:Service1Soap">...</wsdl:binding>

remove the second binding and use the first one that is <wsdl:binding name="Service1Soap" type="tns:Service1Soap">...</wsdl:binding>

if this provides you with useful information and if this is what you where looking for then please mark it as a solution for other benefits.

Rahul Mukherji 35Rahul Mukherji 35
(Tried and  Tested)In case, some one comes and looks for the answer. In your wsdl file, if you see the binding type for soap 1.1 and soap 1.2, then you could remove the other binding type with soap1.2 and also remeber to remove the port type for soap 1.2 . This would resolve the issue.

In case you only have soap1.2, you could try changing the wsdl file for the binding type and port type to 1.1 .
(Did not try)To do so, you can remove the digit 12 from the binding type and port type and save the wsdl file again and try to parse it. Hope that should do the job.