Issue

• There is a strange behaviour with the SOAPClient that generates empty xml objects for non required fields. Precisely speaking, it is observed that if a complex type of message (element in SOAP message) contains a null then SOAPClient sends an empty element (as well as an empty child element). To some users it shouldn't be a desired behaviour and ESB should rather omit the entire parent-child elements altogether, as it might cause unnecessary NullPointerException to user's code consuming the SOAP messages.
  Is there a way to fix this problem so that SOAPClient generates the SOAP messages following the pattern mentioned above?