soapui
soapui copied to clipboard
SmartBear
XML Default Response Editor in SOAP Project
Is there a way to set the XML view as the default response editor for soap projects? In the latest version 5.7.0 the response is RAW, in previous versions the XML was fine. This is very time consuming for each update that needs to be performed on the test case. Thanks
I have the same problem. It was supposed to automatically detect the content type and open that view, as described below. This works for JSON responses but not for XML.
- Now, SoapUI opens a response editor that matches the response content type. For example, it opens the JSON editor if a response has JSON content.
SOAP Request uses the Content-Type header of the response to decide whether to open XML or Raw tab.
If the Content-Type contains:
- only "text/xml", it shows the response in XML tab
- if it contains also the encoding information, e.g. text/xml;charset=UTF-8, the response is displayed in the Raw tab
REST Request seems to be OK.
if you download 5.6.1 last stable version from https://www.soapui.org/downloads/soapui/soapui-os-older-versions/
it works and display xml tab by default as we used to it
log4j vulnerability also fixed in 5.6.1 if you download again. it uses log4j 2.16 which is fixed version and have necessary lookup variable set in soapui bat file to prevent latest vulnerability CVE-2021-44228
so until soaui fix v 5.7 raw tab issue, you may use 5.6.1 But download again
Imran Barolia
In the release notes they write about it. But I guess important set this in some configuration at preferences. Please, think about it.
Does anyone know if a fix is being worked on for this issue? I tried to go back to version 5.6.1 after upgrading to 5.7.0 but since my projects had been upgraded I got a warning when opening the previous version and the projects were not fully working in version 5.6.1 anymore. So that doesn't seem like a usable solution to this issue.
I have created a pull request to fix this issue: https://github.com/SmartBear/soapui/pull/725
It needs to be merged to another version of SoapUI.
When could we expect to see this fixed in a 5.7.1 release? It's a very annoying user experience to always have to click back to the XML tab.
I can only agree, this bug is very annoying in the daily work routine.
You can download the source code and apply karelhusa's solution, then you just have to generate the jar with maven and problem solved.
Hello. I have the same problem on this side. DEV fix the problem as soon as possible please
The current solution as stated before is to go back to 5.6.1 unless something is required/needed from the 5.7 version.
This is probably on the "minor" side of issues and will just have to wait until it is incorporated into a release. (not a dev just looking at it from practical perspective)
The current solution as stated before is to go back to 5.6.1 unless something is required/needed from the 5.7 version.
This is probably on the "minor" side of issues and will just have to wait until it is incorporated into a release. (not a dev just looking at it from practical perspective)
Like I have mentioned previously it is not a usable workaround to go back to version 5.6.1 if you have already upgraded your projects, because they will not work with the older version of SoapUI.
Guys, as I can see a lot of people struggling with this issue, I built a workaround for the time being, until the new release of SoapUI comes out. See this short article how to do that.
I have tested @karelhusa 's solution and it works perfectly. Thank you very much 👍
For those who are skeptical like me; I have compared the old jar and new jar, decompiled the changed class file and the only difference is this:
return contentType.toLowerCase().contains("xml") ? 2 : 0; return contentType.toLowerCase().endsWith("xml") ? 2 : 0;
(sorry @karelhusa , you know you can never trust the internet)
If you scrolled down until here and is still having the same issue, you can install the version 5.6.1 (as mentioned above by @imranbarolia): https://www.soapui.org/downloads/soapui/soapui-os-older-versions/
I've uninstalled the version 5.7.0 and 5.6.1 worked like a charm.
Is this tool still maintained or should I start looking for something else? It's been close to a year since the original report with the only alternative being to downgrade with seemingly security vulnerabilities.
I understand that this is an open source project, but it's still advertised on the main website next to a paid product.
