This content has been marked as final.
Show 6 replies
-
1. Re: Support SOAP 1.1 and SOAP 1.2 in the same Endpoint
Ramesh R Nov 16, 2010 10:33 AM (in response to Ramesh R)Seems like nobody is find this interesting
Anyways, I got the solution. If you are going to support both soap 1.1 and soap 1.2, then soap 1.2 definition alone in WSDL is enough.
If there is a request from soap 1.1 then CXF will respond with soap 1.1. So, there is no need of separate port or definition needed for soap 1.1 if you are supproting soap 1.2.
Ramesh
-
2. Re: Support SOAP 1.1 and SOAP 1.2 in the same Endpoint
Jim Ma Nov 17, 2010 5:30 AM (in response to Ramesh R)I think this also works : remove the @BindingType annotation and keep the soap11 and soap 12 binding in the wsdl file .
-
3. Re: Support SOAP 1.1 and SOAP 1.2 in the same Endpoint
Ramesh R Nov 17, 2010 5:46 AM (in response to Jim Ma)It doesn't work even if there is no @BindingType annotation.
-
4. Re: Support SOAP 1.1 and SOAP 1.2 in the same Endpoint
Fabricio Raphael Nov 18, 2010 11:59 AM (in response to Ramesh R)In same class, can I have any methods with SOAP 1.1 and others with SOAP 1.2?
-
5. Re: Support SOAP 1.1 and SOAP 1.2 in the same Endpoint
Ramesh R Nov 22, 2010 1:27 AM (in response to Fabricio Raphael)But, why do you need that? since the framework supports backward compatibility..
-
6. Re: Support SOAP 1.1 and SOAP 1.2 in the same Endpoint
Fabricio Raphael Nov 24, 2010 7:12 AM (in response to Ramesh R)Because my client wants this way!