Virtual service is customized with a Web Service Execution (XML) step and it is adding the WS-Addressing headers during runtime, which causes the service to return an unexpected error.
For example, In the below request <wsa>.. </wsa> tags are added automatically.
<tns:Envelope xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/"> <tns:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> <Testsoap:test_id xmlns:ttsoap="http://xxx.com/ws/soapheaders">3xc576...</Testsoap:test_id> <wsa:To>http://xxxx.com/Test123</wsa:To><wsa:MessageID>urn:uuid:34-5647-878</wsa:MessageID><wsa:Action>urn:xxxResponse</wsa:Action> </tns:Header> <tns:Body> ....... ....... </tns:Body></tns:Envelope>Tried "Use WS-Addressing" option turned off in the Web Service Execution (XML) step-->Addressing tab but still the headers are being added. Is there a way to resolve this and prevent the headers from being added?
Service Virtualization 10.8.3.1
Axis code changes in 10.8.3.1 caused the issue.
In 10.8.3.1, some changes happened to axis files. Making the below changes on the VSE server should resolved the issue.
1. Stop the VSE.
3. Save the file.
4. Start the VSE.