cancel
Showing results for 
Search instead for 
Did you mean: 

Import WSDL file along with XSD

Former Member
0 Kudos

Hi,

I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).

If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.

How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?

Could you please help me out…?

Accepted Solutions (0)

Answers (2)

Answers (2)

Shabarish_Nair
Active Contributor
0 Kudos

Not sure of this approach, but try to zip both files and then upload that zip file, Might find luck !!!

Former Member
0 Kudos

if i import zip file in imported Archive .. how will i use in Message Interface..

can you please give me step by step for this please...

Shabarish_Nair
Active Contributor
0 Kudos

try to create a ED with WSDL option and then try to load the zip file (use all files when u browse) in this case.

and tell me if it worked ... i am just tryin a trial and error method here !!!

Former Member
0 Kudos

created ED with WSDL and loaded the Zip file. in imported Archive.. but i did not understand how can i inter relate both ED and Zip.

Former Member
0 Kudos

Hi

<i>when i check the Messages tab i can see all the message names but my wsdl file has complex type which is defined in the XSD file. Problem comes when i am doing Message Mapping. Let i explain u in this way..

I have in source

User name

Password fields

but in target i have complex type as fx:authInfo..</i>

Even from complex type the connection is internally created by the WSDL. In your WSDL, do u have a messsage which contains fields for the userid and password. Just map your structure fields to the target message.

What do u mean when u are saying there is mapping in problem. Do u mean the Data type??

Regards

Vijaya

Former Member
0 Kudos

in Target Message i have something like this

Tree Occurrences

authoInfo 1..1 xx:AuthInfo

Former Member
0 Kudos

first i will tell how my wsdl file is defined

<xs:element name="authInfo" type="<b>xx:AuthInfo</b>"> <xs:annotation> <xs:documentation xml:lang="en"> Authentication information </xs:documentation> </xs:annotation> </xs:element>

and in my xsd file for xx:AuthInfo

<xs:complexType name="AuthInfo">

<xs:sequence>

<xs:element name="acctName" type="tns:CustName">

<xs:annotation>

<xs:documentation xml:lang="en">

account name.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element name="password" type="tns:AcctPswd">

<xs:annotation>

<xs:documentation xml:lang="en">

Specify the password </xs:documentation>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"

but "AuthInfo" has two inputs.

this is how my Target Message Look like

Tree Occurences Type

authInfo 1..1 xx:AuthInfo

i hope i have cleared u..

Former Member
0 Kudos

Hi,

You just have to import the WSDL as External Definition.

there in the Message tab you will see the list of xsd that have got imported.

You can use the same for MT etc.

Regards

Vijaya

Former Member
0 Kudos

thanks for ur reply..

when i check the Messages tab i can see all the message names but my wsdl file has complex type which is defined in the XSD file. Problem comes when i am doing Message Mapping. Let i explain u in this way..

I have in source

User name

Password fields

but in target i have complex type as fx:authInfo..

this fx:authInfo is defined in XSD file as

<xs:complexType name="AuthInfo">

<xs:sequence>

<xs:element name="acctName" type="tns:CustName">

<xs:annotation>

<xs:documentation xml:lang="en">

account name.

</xs:documentation>

</xs:annotation>

</xs:element>

<xs:element name="password" type="tns:AcctPswd">

<xs:annotation>

<xs:documentation xml:lang="en">

password </xs:documentation>

</xs:annotation>

</xs:element>

</xs:sequence>

</xs:complexType>

for mapping this two fields i have to have two fields in the Target as well. but i am not getting that.

i hope i am clear to u..