What determine namespace when JSON is converted to XML
I am using SoapUI Pro 5.0.0 (non trial)
I have two REST calls I'm making to the same endpoint. This is done from different test cases in different test suites.
The endpoint is defined in a project level property and is something.example.com/my/foo/bar. The actual test step references the project property as the endpoint.
I am under the impression that the request endpoint determines the namespace of the XML when JSON is converted to XML. This cannot be correct as that is not the behavior I'm seeing.
The first response gets the namespace of "something.example.com/my/foo/foo/bar"
The second response gets the namespace of "other.example.com/my/foo/bar"
I should note that "other.example.com/my/foo/bar" is a valid endpoint for the request, but is not the endpoint being used.
My questions is thus why is this happening?
Does SoapUI actually use something different from the request endpoint when determining the namespace and for some reason my specific setup of servers is causing this to differ?
I have two REST calls I'm making to the same endpoint. This is done from different test cases in different test suites.
The endpoint is defined in a project level property and is something.example.com/my/foo/bar. The actual test step references the project property as the endpoint.
I am under the impression that the request endpoint determines the namespace of the XML when JSON is converted to XML. This cannot be correct as that is not the behavior I'm seeing.
The first response gets the namespace of "something.example.com/my/foo/foo/bar"
The second response gets the namespace of "other.example.com/my/foo/bar"
I should note that "other.example.com/my/foo/bar" is a valid endpoint for the request, but is not the endpoint being used.
My questions is thus why is this happening?
Does SoapUI actually use something different from the request endpoint when determining the namespace and for some reason my specific setup of servers is causing this to differ?
