cancel
Showing results for 
Search instead for 
Did you mean: 

Defining own data types for a Web Service

former_member198060
Participant
0 Kudos
74

Dear experts,

I am working on a scenario where I need to call an external Web Service.

The WSDL for this Web Service was provided to me but is very complex and inlcudes xsd:any subelements which are not described in detail in the WSDL.

Therefore I would like to model the message myself instead of using the WSDL.

Now I already have a question, using the standard conventions for Data Types DT_Name and Message Types MT_Name I am not sure how to handle the root Element. As the WSDL defines a specific root element that is expected from the Web Service, do I need to call my Data Type and Message Type by this specific name which is not in line with the standard naming conventions? Or is there a way to ignore the root Element which would be the Data Type name and use my first child element as the root element for the message later?

View Entire Topic
jagdishwar_b
Active Participant
0 Kudos

>The WSDL for this Web Service was provided to me but is very complex and inlcudes xsd:any subelements which are not described in detail in the WSDL.

>Therefore I would like to model the message myself instead of using the WSDL.

generally, if you recreate DTs MTs for the webservice, it is like undermining the real purpose/strength of WSDL.

the types element of wsdl does this job for us.

if the webservice provider used xsd:any elements, then it is better to ask webservice provider to refine the xsd types in wsdl to make it specific.

regards,

BJagdishwar.