httpResponseStatus="" proptery causes errors in soapUI 5.x
Upon opening a soapUI 4.6.4 project in ANY version of soapUI 5.x, soapUI 5.x leaves the listener Test Step's config --> response --> httpResponseStatus property in an unsupported state, which then causes NumberFormatException exceptions when you try to run the listener tests. This happens in every 5.x version of soapUI. This same property causes no issues in 4.x.
This specifically happens for any 4.6.4 listener test step that has the following child element: <con:response httpResponseStatus="">
After saving in soapUI 5.x this element is updated to: <con:response httpResponseStatus="" id="38c11fe9-1837-40ca-809e-7dab84252058">
However, if you create a new test step in soapUI 5.x, the equivalent element is: <con:response id="38c11fe9-1837-40ca-809e-7dab84252058">
The updated test steps fail with the numberFormatException in soapUI 5.x, however newly created test steps, with identical content, work without issue, and the only difference is the httpResponseStatus="" property.
See attached log for full exception.
Expected Result:
When soapUI encounters this scenario, it should remove the httpRepsponseStatus="" from the test step's config <con:response> element, or it should handle it without error if if left in place.
Work Around:
Open your soapUI project in a text editor and remove httpResponseStatus="" from all of your test step's <con:response> elements. After doing this, the affected test steps will work in soap 5.x.
Note:
The response element normally shows up right after your listener's path and port elements:
e.g. <con:path>/somePath</con:path><con:port>8080</con:port><con:response httpResponseStatus=""><con:settings>
This specifically happens for any 4.6.4 listener test step that has the following child element: <con:response httpResponseStatus="">
After saving in soapUI 5.x this element is updated to: <con:response httpResponseStatus="" id="38c11fe9-1837-40ca-809e-7dab84252058">
However, if you create a new test step in soapUI 5.x, the equivalent element is: <con:response id="38c11fe9-1837-40ca-809e-7dab84252058">
The updated test steps fail with the numberFormatException in soapUI 5.x, however newly created test steps, with identical content, work without issue, and the only difference is the httpResponseStatus="" property.
See attached log for full exception.
Expected Result:
When soapUI encounters this scenario, it should remove the httpRepsponseStatus="" from the test step's config <con:response> element, or it should handle it without error if if left in place.
Work Around:
Open your soapUI project in a text editor and remove httpResponseStatus="" from all of your test step's <con:response> elements. After doing this, the affected test steps will work in soap 5.x.
Note:
The response element normally shows up right after your listener's path and port elements:
e.g. <con:path>/somePath</con:path><con:port>8080</con:port><con:response httpResponseStatus=""><con:settings>