Hey @obruxelle
well - I never saw an issue in SoapUI like that before! I think that's a defect.
I'm assuming the RAW is correct and the JSON tab is incorrect?
I'm wondering if you'd still get the problem if you forced the response to be in XML instead of json? perhaps there's an issue with the jsonparser that's the cause of this (probably not - cos it displays ok in the RAW I'm guessing....) - but still.
If on your request (that generates this weird response), you add in an 'Accept' header with the value 'application/xml' - this will force the response to be returned with Content-Type header value of application/xml (payload will be xml). I'm wondering if you'd still get this disparity you're seeing if you use the xmlparser rather than the jsonparser?
Worth a try maybe? you're not really losing anything shifting from one to another....
ta
Rich
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
