Null Wsdl Fields Omitted in soap Request

(Doc ID 1135316.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle Weblogic Server - Version: 10.3 and later   [Release: and later ]
Information in this document applies to any platform.


In WLS, following problem was experienced with SoapRequest which is being generated. An empty field is not replaced with xsi:nil="true" in the soap message.

For Eg:-
If the following complex element defined in wsdl
<xsd:complexType name="XXXXXXXXXXXXXXXXXX">
<xsd:element form="qualified" name="id_empl_user">
<xsd:restriction base="string">
<xsd:maxLength value="8"/>
<xsd:whiteSpace value="preserve"/>
<xsd:element form="qualified" name="id_ba">
<xsd:restriction base="long">
<xsd:minInclusive value="0"/>
<xsd:maxInclusive value="9999999999"/>

when we populate only id_empl_user the following request is generated

<env:Envelope xmlns:env="" xmlns:xsi=""><env:Header/>
<cus:sample xmlns:cus="YYYYY">

but this is not generating the other attribute since the value is null

Is there anything to be configured in the WebLogic server for resolving this issue ?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms