AnsweredAssumed Answered

Namespace issue in .vsi request

Question asked by swathib on Aug 2, 2018
Latest reply on Aug 8, 2018 by Joel NeSmith

Hi,

 

I’m developing virtual services using request & response pairs. Here marked namespaces are changing when I integrate virtual service in my API. (API internally talks with virtual service and request sent to virtual service. Mainly namespaces are changed here).  So my API is receiving default META response from virtual service.

 

Is there a way to avoid/omit namespaces in .vsi request? I’ve chosen Match style as “Exact” because response will vary from id. Please provide your suggestions here?

Request used for implementing virtual service :
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<ns2:WFContext
xmlns:ns6="http://xxxx/address/2003/"
xmlns:ns5="http://xxxx/communication/email/2003/"
xmlns:ns4="http://xxxx/communication/2003/"
xmlns:ns3="http://xxxx/communication/phone/2003/"
xmlns:ns2="http://***/entity/message/2003/">
<ns2:messageId>xxxx</ns2:messageId>
<ns2:sessionId>***</ns2:sessionId>
<ns2:creationTimestamp>xxxx</ns2:creationTimestamp>
</ns2:WFContext>
<ns3:hulaContext
xmlns:ns3="http://***/provider/HCFG/entity/envelope/2004/"
xmlns:ns2="http://***/entity/message/2003/">
<ns2:version>0</ns2:version>
</ns3:hulaContext>
</soap:Header>
<soap:Body>
<ns8:process
xmlns:ns2="http://***/entity/message/2003/"
xmlns:ns3="http://***/HCFG/entity/envelope/2004/"
xmlns:ns4="http://xxxx/communication/phone/2003/"
xmlns:ns5="http://xxxx/communication/2003/"
xmlns:ns6="http://xxxx/communication/email/2003/"
xmlns:ns7="http://***/communication/address/2003/"
xmlns:ns8="http://xxxdata/***/2016/" contentType="application/json" encoding="charset=utf-8">&lt;![CDATA[{"request":{"id":"1000"}}]]&gt;
</ns8:process>
</soap:Body>
</soap:Envelope>


Request from API to virtual service:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<ns2:WFContext
xmlns:ns6="http://***/communication/address/2003/"
xmlns:ns5="http://***/communication/email/2003/"
xmlns:ns4="http://***/communication/2003/"
xmlns:ns3="http://***/communication/phone/2003/"
xmlns:ns2="http://***/message/2003/">
<ns2:type>***</ns2:type>
</ns2:WFContext>
<ns3:hulaContext
xmlns:ns3="http://***/provider/HCFG/entity/envelope/2004/"
xmlns:ns2="http://***/entity/message/2003/">
<ns2:version>0</ns2:version>
</ns3:hulaContext>
</soap:Header>
<soap:Body>
<ns8:process
xmlns:ns2="http://***/message/2003/"
xmlns:ns3="http://***/communication/phone/2003/"
xmlns:ns4="http://***/communication/2003/"
xmlns:ns5="http://***/communication/email/2003/"
xmlns:ns6="http://***/communication/address/2003/"
xmlns:ns7="http://***/provider/x/entity/envelope/2004/"
xmlns:ns8="http://***/provider/x/data/***/2016/" contentType="application/json" encoding="charset=utf-8">&lt;![CDATA[{"request":{"id":"1000"}}]]&gt;
</ns8:process>
</soap:Body>
</soap:Envelope>

 

Outcomes