A Nillable Element Is Not Correctly Marshaled When Returned From A Spring Context
(Doc ID 1448789.1)
Last updated on JANUARY 09, 2024
Applies to:
Oracle SOA Suite - Version 11.1.1.4.0 to 11.1.1.5.0 [Release 11gR1]Information 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:
A workaround is to use an element with an optional child element, but this increases the verbosity of the xml.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |