SmartBear / soapui

SoapUI is a free and open source cross-platform functional testing solution for APIs and web services.
http://www.soapui.org
Other
1.54k stars 607 forks source link

XML Default Response Editor in SOAP Project #721

Open albertapiadev opened 2 years ago

albertapiadev commented 2 years ago

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

MDagni commented 2 years ago

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.
karelhusa commented 2 years ago

SOAP Request uses the Content-Type header of the response to decide whether to open XML or Raw tab.

If the Content-Type contains:

REST Request seems to be OK.

imranbarolia commented 2 years ago

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

derritter88 commented 2 years ago

Same issue on my side.

JKL888 commented 2 years ago

Since updating to 5.7 , I am having this same issue.

zetoniazzo commented 2 years ago

Any solution to this?

zetoniazzo commented 2 years ago

In the release notes they write about it. But I guess important set this in some configuration at preferences. Please, think about it.

sigurdurg commented 2 years ago

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.

karelhusa commented 2 years ago

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.

jpraet commented 2 years ago

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.

computerkram commented 2 years ago

I can only agree, this bug is very annoying in the daily work routine.

MJHeijster commented 2 years ago

It's bizarre that this bug still hasn't been fixed...

serloar commented 2 years ago

You can download the source code and apply karelhusa's solution, then you just have to generate the jar with maven and problem solved.

MDagni commented 2 years ago

you just have to generate

meaning install and learn maven first 😄

xs2bharat commented 2 years ago

Facing same issue in 5.7.0

edhCoder commented 2 years ago

Do devs look at these comments? It's April already

k0d3r1s commented 2 years ago

please fix it, it's annoying

jiridusil commented 2 years ago

I have the same issue in 5.7.0. Please, fix it asap. Thanks

robbyappel commented 2 years ago

Hello. I have the same problem on this side. DEV fix the problem as soon as possible please

Zaf9670 commented 2 years ago

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)

sigurdurg commented 2 years ago

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.

karelhusa commented 2 years ago

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.

MDagni commented 2 years ago

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)

Xfox1 commented 2 years ago

Same issue!

joaquinfigueroa commented 2 years ago

thanks so much @karelhusa, this works !!

cstazo commented 2 years ago

@karelhusa appreciate the workaround!

Jefferson227 commented 1 year ago

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.

drazhan commented 1 year ago

@karelhusa It works!!! Thanks a lot!!!

linaori commented 1 year ago

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.

karelhusa commented 1 year ago

@linaori We need to make the conclusion ourselves; this is mine.

MDagni commented 1 year ago

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.

Looks like they don't do any updates on this tool anymore. You can try @karelhusa 's solution here, it works very well for me. https://github.com/SmartBear/soapui/issues/721#issuecomment-1114653409

PatelsTech commented 1 year ago

This is really annoying bug but finally today I found a workaround. It is, remove encoding from request properties (unless you have issues and must keep encoding in request), and it should start showing response in xml tab. When I had "UTF-8" , it was showing raw response. I hope this helps.

andy-fitch commented 1 year ago

I'm using v5.7.0 and the default response is going to the raw tab - REALLY REALLY ANNOYING that we have to go and change tabs for every single request for it to show in xml view. Also very surprised that is issue is outstanding for so long - It's now April of 2023 - is this tool no longer being supported?

mstrey commented 1 year ago

After so many time and this annoying bug still not fixed. Why is so hard to fix this?

karelhusa commented 1 year ago

After so many time and this annoying bug still not fixed. Why is so hard to fix this?

@mstrey, you can take this as an answer: https://github.com/SmartBear/soapui/graphs/code-frequency .

CasualDeveloper commented 11 months ago

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.

Hi Karel, could you rebuild this for v5.7.1 please? :D

karelhusa commented 11 months ago

@CasualDeveloper Hi, see https://github.com/karelhusa/soapui/tree/xml_contentType_fix_5.7.1/bin

The installation procedure same as before: https://www.linkedin.com/pulse/fix-xml-content-type-recognition-soapui-570-karel-husa/

I hope it helps.

rgisiger commented 11 months ago

See https://github.com/karelhusa/soapui/tree/xml_contentType_fix_5.7.1/bin

The installation procedure is the same as before: https://www.linkedin.com/pulse/fix-xml-content-type-recognition-soapui-570-karel-husa/

For MacOS, just replace the soapui-5.7.1.jar file in /Applications/SoapUI-5.7.1.app/Contents/java/app/bin with the one provided by @karelhusa (thank you by the way)

I confirm it works as well on Mac.

brihuega commented 10 months ago

After more than a year waiting for 5.7.1 release, I've just installed it and this annoying bug is still there. It's incredible. The patch by @karelhusa is working fine. Karel, you are great!

vampirepapi commented 10 months ago

@karelhusa could you please give me brief idea how you fixed this issue?

karelhusa commented 10 months ago

@vampirepapi I made a code fix and built the SoapUI JAR. You can build the JAR from the source code yourself if you prefer that.

CasualDeveloper commented 8 months ago

@CasualDeveloper Hi, see https://github.com/karelhusa/soapui/tree/xml_contentType_fix_5.7.1/bin

The installation procedure same as before: https://www.linkedin.com/pulse/fix-xml-content-type-recognition-soapui-570-karel-husa/

I hope it helps.

Hi Karel,

Thanks for the 5.7.1 patch. Unfortunately, 5.7.2 was just released and issue is still present. Could you update it for 5.7.2? That would be appreciated so much!

LeJoris commented 8 months ago

I don't use SOAP UI much but even I am annoyed by reponse defaulting to RAW

karelhusa commented 7 months ago

Hi Karel,

Thanks for the 5.7.1 patch. Unfortunately, 5.7.2 was just released and issue is still present. Could you update it for 5.7.2? That would be appreciated so much!

Hi @CasualDeveloper, I have added the 5.7.2 version as well, see https://www.linkedin.com/pulse/fix-xml-content-type-recognition-soapui-570-karel-husa/ .

denissand commented 3 months ago

It's unbelievable 2+years later this simple but very annoying bug is still not fixed. Many thanks @karelhusa for the patch.

lhall-amphibee commented 2 months ago

Can't believe we have to do this after 2 yrs but here we are. Thanks @karelhusa for the patched JAR.

sedwards-ws commented 2 months ago

Many thanks for this fix @karelhusa, it has been driving me nuts since the release of 5.7.0, Smart Bear telling people to roll back to v5.6 as a fix is not on.