My Oracle Support Banner

How to manipulate xml namespace prefix in SOAP Request of Outbound Web Service? (Doc ID 1362987.1)

Last updated on NOVEMBER 12, 2019

Applies to:

Siebel Sales Enterprise - Version 8.0 [20405] and later
Information in this document applies to any platform.


The Question was raised:

How to introduce explicit xml name space prefix in the payload of SOAP request, sending out of Outbound Web Service of Siebel 8.1.1 (need to make XML be generated same way as in Siebel 7.7)?

NOTE:  In case the Outbound Web Service received payload for SOAP Request not via "SiebelMessage" of an Integration Object (of the request) but via generic "XMLHierarchy" input parameter, that represents any property set structure. As result, the Web Service name space URI was assigned to the root item of the hierarchy.
Siebel 7.7 example of SOAP Body payload for WS operation: "m1" and WS URI: ""
<ns:m1 xmlns:ns=""
Siebel 8.x example of the same call:
<m1 xmlns=""
Despite of same identification of the name space for the XML tag, the external application (Web Service Provider) could not parse the incoming SOAP request well, when explicit name space prefix was not used.
Solution was asked to amend creation of the XML message in Siebel 8.x to make it be present as in Siebel 7.7.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.