0 Replies Latest reply on Aug 3, 2004 11:38 AM by Simon Morgan

    What causes hrefs in response messages

    Simon Morgan Newbie

      Hi,

      I'm getting a response message back roughly along the lines of:

      <ns1:processAuthorisationRequestResponse soapenv:encodingStyle="..." xmlns:ns1="...">
       <ns1:processAuthorisationRequestReturn href="#id0"/>
      </ns1:processAuthorisationRequestResponse>
      
      <multiRef id="id0"
      soapenc:root="0"
      soapenv:encodingStyle="..."
      xsi:type="..."
      xmlns:soapenc="..."
      xmlns:ns2="...">
      ...
      </multiref>


      Please say if I taken out too much detail.

      I understand what the href + multiRef is doing, however some of my web svc client code doesn't seem to like this. It is expecting

      <processAuthorisationRequestReturn>
      ...
      </processAuthorisationRequestReturn>


      Whilst I'm assuming that generated response is a valid SOAP message, if I can alter how the response is generated / understand why the href occurs instead of it being put in directly beneath the elements, this would really be helpful.

      (I am investigating get the client to parse this correctly, however I'm - as is everyone else in the world - under a deadline to get it working :-> )

      Thanks in advance for any help.

      Cheers

      Simon