AnsweredAssumed Answered

WSDL XML Name Space and VSI matches

Question asked by sdetweil2 on Jan 4, 2016

One of my dev teams has been creating a service, and doing well.. using a test driver tool, like postman to send requests..

 

the message starts out with

 

<soapEnv:addPartner ........ etc

  <partner>

 

now he goes to test the real app to the service and gets a different message

 

<soapEnv:Envelope........

<soapenv:Header/>

   <soapEnv:body>

       <v9:addPartner.....>

           <partner>

 

his vsi has has addPartner as the operation.

but the request has Envelope

 

the v9 tag is not in the attributes tab of the vsi for this transaction

 

without rerecording, or starting from the wsdl (which has v9 namespace defined, but the service from wsdl didn't use it)

 

is there an easy way to fixup his VSI?

 

I don't see any discussion of the use of namespaces in the online help.

Outcomes