Last updated on OCTOBER 18, 2016
Applies to:
Oracle SOA Platform - Version: 11.1.1.4.0 to 11.1.1.5.0 - Release: 11gR1 to 11gR1Information in this document applies to any platform.
Symptoms
- In a SOA composite application, a Spring context is used which has a response element that contains a required nillable element
- The issue is that this element is not marshaled with xsi:nil="true" but the element is not in the response at all. As a result, the response is invalid
You obtain something like this:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<env:Body>
<testNillableNumberResponse xmlns="http://testnilelement/">
<return xmlns="" xmlns:ns0="http://xml.someDomain.com/rsg/mpl"/
</testNillableNumberResponse>
</env:Body>
</env:Envelope><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<env:Body>
<testNillableNumberResponse xmlns="http://testnilelement/">
<return xmlns="" xmlns:ns0="http://xml.someDomain.com/rsg/mpl">
<ns0:number xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
</return>
</testNillableNumberResponse>
</env:Body>
</env:Envelope>A workaround is to use an element with an optional child element, but this increases the verbosity of the xml.
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