1 Reply Latest reply on Aug 18, 2011 8:22 AM by Flex harUI

    Flex SOAP 1.1 specification issue

    rtripathi

      Hi,

      In our project we are integrating flex with Websphere Enterprise Service Bus(ESB). Flex will call a web service which is exposed by ESB through LCDS configuration. here is the SOAP request message sent by flex to ESB.

       

      <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SOAP-ENV:Body>
      <app:loadApproval xmlns:app="http://approval.common.vo.state.cws.us/">
      <arg0>
      <actionChecked xsi:nil="true"/>
      <approvalDetailList xsi:nil="true"/>
      <approvalEntity>
      <approveDate xsi:nil="true"/>
      <approver xsi:nil="true"/>
      <comments xsi:nil="true"/>
      <id>1000755</id>
      <level xsi:nil="true"/>
      <module>REF</module>
      <operation xsi:nil="true"/>
      <otherParam xsi:nil="true"/>
      <otherParam2 xsi:nil="true"/>
      <otherParam3 xsi:nil="true"/>
      <otherParam4 xsi:nil="true"/>
      <otherParam5 xsi:nil="true"/>
      <reason xsi:nil="true"/>
      <requestDate xsi:nil="true"/>
      <requester>james1</requester>
      <sendbackDate xsi:nil="true"/>
      <sequenceNumber xsi:nil="true"/>
      <status xsi:nil="true"/>
      <subtype xsi:nil="true"/>
      <subtype2 xsi:nil="true"/>
      <subtype3 xsi:nil="true"/>
      <subtype4 xsi:nil="true"/>
      <subtype5 xsi:nil="true"/>
      <subtypeID xsi:nil="true"/>
      <subtypeID2 xsi:nil="true"/>
      <subtypeID3 xsi:nil="true"/>
      <subtypeID4 xsi:nil="true"/>
      <subtypeID5 xsi:nil="true"/>
      <taskId xsi:nil="true"/>
      <type>CPS</type>
      </approvalEntity>
      <approvalStatus xsi:nil="true"/>
      <latestApprovalEntity xsi:nil="true"/>
      <selectedRow>0</selectedRow>
      <userList xsi:nil="true"/>
      </arg0>
      </app:loadApproval>
      </SOAP-ENV:Body>
      </SOAP-ENV:Envelope>    

       

      The above highlighted elements are not complined with SOAP 1.1 specification. As the SOAP 1.1 Specification says:
      A NULL value or a default value MAY be represented by omission of the accessor element. A NULL value MAY also be indicated by an accessor element containing the attribute xsi:null with value '1' or possibly other application-dependent attributes and values.


      Now Websphere ESB requires the request to be SOAP 1.1 complaint and if SOAP element is null than either it should not be present in SOAP message or null element should have xsi:null="1" instead of  xsi:nil="true".

       

      Please provide your views to make Flex SOAP request complined with SOAP 1.1 specification.