finsterwalder
16 years agoOccasional Contributor
SoapUI has a problem with a namespace
Hi there,
I have a problem with SoapUI, where I currently think SoapUI is not working correctly.
When I send the following soap request (via the CXF-Framework) to a soapUiMock, SoapUi responds with an error:
someAddress
text
Response:
Missing operation for soapAction [http://www.xyz.com/myurl/opName] and body element [{http://www.xyz.com/mynamespace}address] ...
SoapUI responds correctly, if I omit the namespace in the address-tag. So the following XML is what SoapUI expects:
someAddress
text
When I let SoapUI generate a request from the WSDL, that is also what is generated.
Why is SoapUI thinking, that address doesn't have a namespace?
And here is the WSDL for all of that:
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.xyz.com/mynamespace"
xmlns:envelope="http://www.xyz.com/othernamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
name="myName"
targetNamespace="http://www.xyz.com/mynamespace">
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.xyz.com/mynamespace"
xmlns:tns="http://www.xyz.com/mynamespace"
xmlns:envelope="http://www.xyz.com/othernamespace">
name="address"
element="tns:address" />
name="request"
element="envelope:someElement" />
name="response"
element="envelope:someOtherElement" />
name="myBinding"
type="tns:portName">
style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
soapAction="http://www.xyz.com/myurl/opName" />
name="myName"
binding="tns:myBinding">
location="http://www.xyz.com/myurl" />
I have a problem with SoapUI, where I currently think SoapUI is not working correctly.
When I send the following soap request (via the CXF-Framework) to a soapUiMock, SoapUi responds with an error:
someAddress
Response:
Missing operation for soapAction [http://www.xyz.com/myurl/opName] and body element [{http://www.xyz.com/mynamespace}address] ...
SoapUI responds correctly, if I omit the namespace in the address-tag. So the following XML is what SoapUI expects:
someAddress
When I let SoapUI generate a request from the WSDL, that is also what is generated.
Why is SoapUI thinking, that address doesn't have a namespace?
And here is the WSDL for all of that:
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://www.xyz.com/mynamespace"
xmlns:envelope="http://www.xyz.com/othernamespace"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
name="myName"
targetNamespace="http://www.xyz.com/mynamespace">
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.xyz.com/mynamespace"
xmlns:tns="http://www.xyz.com/mynamespace"
xmlns:envelope="http://www.xyz.com/othernamespace">
name="address"
element="tns:address" />
name="request"
element="envelope:someElement" />
name="response"
element="envelope:someOtherElement" />
name="myBinding"
type="tns:portName">
style="document"
transport="http://schemas.xmlsoap.org/soap/http" />
soapAction="http://www.xyz.com/myurl/opName" />
name="myName"
binding="tns:myBinding">
location="http://www.xyz.com/myurl" />