WLS 10.3.4 - JAXB isNil() becomes "true" after unmarshaling (Doc ID 1340023.1)

Last updated on JUNE 09, 2016

Applies to:

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

Symptoms

After upgrading from WLS 10.3.3 to WLS 10.3.4,noticing isNil() becoming "true" after unmarshaling.
If you are using JAX-WS and the SOAP message contains null value, you will notice this issue.

Please refer to the attached test case
For example: 
SOAP Request
===============
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ser="http://something/Services" xmlns:som="http://something"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/>
<soapenv:Body>
<ser:TestData>
<A1 xsi:nil="true"/>
<B1>value</B1>
</ser:TestData>
</soapenv:Body>
</soapenv:Envelope>

SOAP Response
=================
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:TestDataResponse xmlns:ns2="http://something/Services">Issue
found B1 tag with value but isNil is true.</ns2:TestDataResponse>
</S:Body>
</S:Envelope>


This was not a problem and was working fine in WebLogic Server 10.3.3 and before.

Cause

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