An OE 12.2 SOAP Web Service throws the following exception when a SOAP request contains xs:nil="true" as an attribute for an input TEMP-TABLE parameter:

com.progress.appserv.adapters.camel.soap.CamelSOAPException: Exception during parsing SOAP message
    at com.progress.appserv.adapters.camel.soap.ExchangeSOAPProcessor.parseSoap(ExchangeSOAPProcessor.java:307)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.apache.camel.support.ObjectHelper.invokeMethodSafe(ObjectHelper.java:381)
    at org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:494)
    ...
Caused by: java.lang.NullPointerException: null
    at com.progress.appserv.adapters.camel.soap.CamelSOAPParamArray.procNotOutputResultSetMetaData(CamelSOAPParamArray.java:368)
    at com.progress.appserv.adapters.camel.soap.CamelSOAPParamArray.procNotOutputParam(CamelSOAPParamArray.java:361)
    at com.progress.appserv.adapters.camel.soap.CamelSOAPParamArray.populateParamArray(CamelSOAPParamArray.java:197)
    at com.progress.appserv.adapters.camel.soap.ExchangeSOAPProcessor.setMessageParameters(ExchangeSOAPProcessor.java:1389)
    at com.progress.appserv.adapters.camel.soap.ExchangeSOAPProcessor.makeMessage(ExchangeSOAPProcessor.java:1361)
    at com.progress.appserv.adapters.camel.soap.ExchangeSOAPProcessor.parseSoap(ExchangeSOAPProcessor.java:299)
    ... 86 common frames omitted

For other types of input parameters (e.g. ABL CHARACTER input parameter) the following exception is thrown:

java.lang.NullPointerException
        at com.progress.appserv.adapters.camel.soap.CamelSOAPAppObject.printInputParams(CamelSOAPAppObject.java:294)
        at com.progress.appserv.adapters.camel.soap.CamelSOAPAppObject.runProcedure(CamelSOAPAppObject.java:275)
        at com.progress.appserv.adapters.camel.soap.abl.CamelSOAPAblEndpoint.runProcedure(CamelSOAPAblEndpoint.java:260)
        at com.progress.appserv.adapters.camel.soap.abl.CamelSOAPAblEndpoint.invokeNormal(CamelSOAPAblEndpoint.java:240)
        at com.progress.appserv.adapters.camel.soap.abl.CamelSOAPAblEndpoint.process(CamelSOAPAblEndpoint.java:131)
        at com.progress.appserv.adapters.camel.soap.abl.CamelSOAPAblProducer.process(CamelSOAPAblProducer.java:43)

However, in this case a SOAP response is returned to the client.

 

The SOAP client receives a SOAP Fault similar to the following:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"" xmlns:xsd="http://www.w3.org/2001/XMLSchema"" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">;
   <SOAP-ENV:Header/>
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Client</faultcode>
         <faultstring>An error was detected in the Web Service request. (10894)</faultstring>
         <detail>
            <ns1:FaultDetail xmlns:ns1="urn:soap-fault:details">
               <errorMessage>Exception during parsing SOAP message</errorMessage>
               <requestID>baaad62b-8347-4d2a-8d69-a8f621581a07</requestID>
            </ns1:FaultDetail>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

When the SOAP Web Service is deployed in an OE 11.7 PASOE instance, then there are no problems with processing a similar SOAP request.

The OpenEdge 11.7 PASOE SOAP processor has been replaced with a new SOAP processor in OpenEdge 12.2 which was not taking XML elements with a nil value into account when processing a SOAP request.

Fixed version(s): OpenEdge 12.6, OpenEdge 12.2.11