cancel
Showing results for 
Search instead for 
Did you mean: 

incoherence between request and response

Highlighted
Frequent Contributor

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 the value is well interpreted in the raw request, but when I see the Response XML panel, I see that the xmlns data (first line) is not the correct one.

At the bottom of the response, the href tag indicates the correct value and the data returned is the expected one.

I'm not familiar with XML, maybe the first line has no real impact, or is it a real bug ?

 

thank you

2 REPLIES 2
Highlighted
Community Hero

Re: incoherence between request and response

Do you mind showing the difference with an example? That can help easily understand the issue.


Regards,
Rao.
Highlighted
Frequent Contributor

Re: incoherence between request and response

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

 

 

 

New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors