Forum Discussion

AmitA's avatar
AmitA
Occasional Contributor
11 years ago

[Registered] XML View Not Coming in REST Service Response

Support Team,

When i am sending a JSON request in REST Service, I am able to view the response in JSON Format, Outline Format & Overview Format but not in XML Format.

It Says: "The content you are trying to view cannot be viewed as XML".

This problem is occurring in SoapUI Versions 5.1.0 and 5.1.1. It was working perfect till 5.0

9 Replies

  • Hello,

    There is an internal defect of SOAP-2701 for this issue. Will let you know when this is fixed.


    Regards,
    Marcus
    SmartBear Support
    • SantoshU's avatar
      SantoshU
      Occasional Visitor

      Is there any work around fro the bug SOAP-2701. I am using latest version of SOAPUI 5.2.1, but still hitting this issue. 

       

      Issue is as below.

      "

      When i am sending a JSON request in REST Service, I am able to view the response in JSON Format, Outline Format & Overview Format but not in XML Format.

      It Says: "The content you are trying to view cannot be viewed as XML".

       

      "

       

      But note that , my response works fine on 5.0 version of SOAPUI.

      Is there any setting I need to do on 5.2.1 ?

      • TanyaYatskovska's avatar
        TanyaYatskovska
        Icon for Alumni rankAlumni

        Hi Santoshu,

         

        I can view the response in the XML format in Ready! API 1.4.1. It looks like the issue was fixed here.

        Do you consider moving to Ready! API? If you have a license for SoapUI Pro, SoapUI NG shipped with Ready! API will work for you.

  • Hi,

    By the way, JSON can now be handled natively in SoapUI Pro. There are new JSON assertions such as JsonPath introduced in 5.1 release as an FYI even though you can still use the XPath assertion.

    So, what functionality do you feel you are losing by not being able to see the XML representation of the JSON?



    Regards,
    Marcus
    SmartBear Support
    • mpeeler's avatar
      mpeeler
      Regular Visitor

      Just upgraded from 5.0.0 to 5.1.3 and encountered this problem immediately. Without being able to see the XML representation of a response, how does one construct an XPath expression for (e.g.) assertions, property transfer? The mapping from JSON to XML is not always obvious (e.g. arrays), so without being able to see the XML, this seems like a major hurdle. I have experience of doing this in 5.0, so I can probably figure it out from my existing test cases, but for a new user, it seems to make the system unusable for working with JSON responses of any complexity.

       

      Is there some other feature in 5.1.x that compensates for this? What am I missing?

  • elysialock's avatar
    elysialock
    Occasional Contributor
    So, what functionality do you feel you are losing by not being able to see the XML representation of the JSON?


    Can you use wildcards for JSON assertions? This is really useful for responses that come back with timestamps, for example.

    -E