cancel
Showing results for 
Search instead for 
Did you mean: 

namespace is not shwon correctly

Former Member
0 Kudos

Hi all,

I have a scenario RFC -> XI Webservice. Where the request structure of the We service contains elements from the two different namespaces as shown below:

I have created the a namespace ns1 and the corresponding data types in it. And then i created a complex data type in the name space ns2 which makes use of these data types. Then this Data type is being used by a message type in the namespace ns2 where i have changed the target XML namespace as required by the Webservice.

Now the problem i have is that i want to retain the namespace for intermediate data types as ns1 itself. I don't want them to get overwritten. Can any body please suggest me the reason here?

-


This is what i get:

<ns1:StartNotification xmlns:ns1="http://xml.avaya.com/diamond/schema/2007/07/NotificationAndResponseService">

<sessionId>AAAAABDxRus=7IWOIg==-_2_1</sessionId>

<originator>

<requesterUniqueId>tcsuser8</requesterUniqueId>

<emailResponseMode>none</emailResponseMode>

<emailAddress><value/></emailAddress>

</originator>

<recipientList>

<recipient>

<recipientName>tcsuser8</recipientName>

<role>participant</role>

<contextKeyword/><preferredLang/><timezone/>

<displayName>tcsuser8</displayName>

*******************************************************************

Expected:

<StartNotification xmlns="http://xml.avaya.com/diamond/schema/2007/07/NotificationAndResponseService">

<sessionId>AAAAABDxRtg=7IWI7Q==-_2_1</sessionId>

<originator>

<ns1:requesterUniqueId xmlns:ns1="http://xml.avaya.com/diamond/schema/2007/07/external-common">tcsuser1</ns1:requesterUniqueId>

<ns2:emailResponseMode xmlns:ns2="http://xml.avaya.com/diamond/schema/2007/07/external-common">none</ns2:emailResponseMode>

</originator>

<recipientList authenticate="false" cancelPreviousPerson="false">

<ns3:recipient type="internal" xmlns:ns3="http://xml.avaya.com/diamond/schema/2007/07/external-common">

<ns3:recipientName>tcsuser1</ns3:recipientName>

<ns3:role>participant</ns3:role>

<ns3:displayName>tcsuser1</ns3:displayName>

Thanks and best regards,

Kulwant

Accepted Solutions (0)

Answers (1)

Answers (1)

stefan_grube
Active Contributor
0 Kudos

This is not possible.

You have to create the WSDL with an external tool and upload to PI.

Regards

Stefan