Hi,
The reason you are having this issue is that in v5.0 we implemented a workaround for this. In v5,0 we now remember a namespace for JSON to XML conversion and then overwrite the same namespace so that our generated XPATH should work. This unfortunately breaks the old workaround where the namespace was automatically generated and not static.
What we would recommend is either staying on the 4.6.4 version of SoapUI Pro for this workaround to keep working. Ideally, however, you could use the even newer functionality we released in v5.1 and replace these XPATH assertions for JSON with JSONPath assertions that we now include in v5.1 (
http://www.soapui.org/Downloads/release-notes.html).
Regards,
Giscard
SmartBear Support
