Forum Discussion

krogold's avatar
krogold
Regular Contributor
8 years ago

incoherence between request and response

Hello, I'm currently evaluating SOAP UI Pro and I notices something strange, though non blocking: I have a rest request having an input parameter that I get from another testCase. I can see that th...
nmrao's avatar
nmrao
Icon for Champion Level 1 rankChampion Level 1
8 years ago
Do you mind showing the difference with an example? That can help easily understand the issue.
  • krogold's avatar
    krogold
    Regular Contributor
    8 years ago

    sorry, you're right, here is the xml response:

     

    <Response xmlns="http://10.37.64.243/m2m/fim/items/fim%3Adevice%3ASHUTTER_BLINDS%3A17/operations">
   <entries>
      <e>
         <name>setConfiguration</name>
      </e>
      <e>
         <name>switchOn</name>
      </e>
      <e>
         <name>syncDevice</name>
      </e>
      <e>
         <name>getConfiguration</name>
      </e>
      <e>
         <name>getDeviceClassNames</name>
      </e>
      <e>
         <name>switchOff</name>
      </e>
      <e>
         <name>getConfigurationMetadata</name>
      </e>
   </entries>
   <href>/m2m/fim/items/fim:device:GENERIC_DEVICE_ON_OFF:20/operations</href>
</Response>

    The correct device is the one named in the bottom href field, though it's not the one set in the (top) http request.

    The request is executed properly with the device named at the bottom