Hi,
This was a while back, so I'm not sure I can remember the exact reason for this, but I do believe it has to do with matching the response type internally in soapUI. Without it, all JSON requests converted to XML look the same, and soapUI doesn't know which schema to validate against (mainly when using schema inferrence). As you suggested, adding an option to specify a namespace instead of basing it off the hostname might be the solution. It's in our backlog of issues to fix. A workaround which works for now is to use a
Property Expansion in the XPath match for providing the namespace. The same Property could be used for specifying the endpoint.
Regards,
Dain
SmartBear Sweden