Sandor_Brinkman
16 years agoOccasional Contributor
Wrong namespace prefixes after soap request step creation
Hi,
I am using a different namespaces imports in my xsd:
xmlns:header="http://xyz.com/common/header/1_2"
xmlns:entities="http://xyz.com/basis/shipment/4_0/entities"
After creation of soap request step I am getting this request:
xmlns:_2="http://xyz.com/common/header/1_2" xmlns:ent="http://xyz.com/basis/shipment/4_0/entities">
<_2:Interface>
<_2:MessageID>?
<_2:Process>?
<_2:ProcessName>?
<_2:ProcessInstanceID>?
?
?
My question is why does change soapUI the namespace prfeixes.
From xmlns:header to xmlns:_2 and
From xmlns:entities to xmlns:ent.
It is a bug or can I configure this setting???
I am using soapUI Pro 2.5.1
Thanks & ragards
Arpad
I am using a different namespaces imports in my xsd:
xmlns:header="http://xyz.com/common/header/1_2"
xmlns:entities="http://xyz.com/basis/shipment/4_0/entities"
After creation of soap request step I am getting this request:
<_2:Interface>
<_2:MessageID>?
<_2:Process>?
<_2:ProcessName>?
<_2:ProcessInstanceID>?
My question is why does change soapUI the namespace prfeixes.
From xmlns:header to xmlns:_2 and
From xmlns:entities to xmlns:ent.
It is a bug or can I configure this setting???
I am using soapUI Pro 2.5.1
Thanks & ragards
Arpad