All geek questions in one place

IWAB0399E Error generating Java from WSDL: java.io.IOException: ERROR: Missing <soap: fault> inFault element

I have a WCF 4.0 service for internal use. Another team is trying to use it in Java.

IWAB0399E Error in generating Java from WSDL: java.io.IOException: ERROR: Missing <soap:fault> element inFault "PasswordReuseFaultFault" ...

One source suggests it could be Soap 1.1 vs. Soap 1.2

In fact, my WCF generated WSDL

 <wsdl:fault name="PasswordReuseFaultFault"> <wsp:PolicyReference URI="#blah_blah_blah_PasswordReuseFaultFault_Fault"/> <soap12:fault name="PasswordReuseFaultFault" use="literal"/> </wsdl:fault>

pay attention to <soap12:fault> instead of the expected <soap:fault> . I am sure this is causing the problem.

  • How do I get WCF to create soap 1.1 WSDL?

or

  • What should I tell the Java team so that their tools can understand the new protocol?

Edit:

I found out that basicHttpBinding uses SOAP 1.1 and puts the expected <soap:fault> in WSDL, where wsHttpBinding puts <soap12:fault> (using the SOAP 1.2 specification, I think.)

I found some suggestions that use Axis instead of an IDE tool will give better results, I'm not sure if I can get the Java team to buy this.

+4
source share
1 answer

I found that AXIS2 will work fine with tags. AXIS2 requires very minimal additional configuration for the eclipse IDE . I will try to get java guys to use this.

Here is a good explanation of making SOAP 1.1 and SOAP 1.2 available to the WCF service .

+2
source

Source: https://habr.com/ru/post/1310430/

More articles:


All Articles