1 Topic by WSDL_Guest

  • WSDL_Guest
  • New member
  • Offline
  • Registered: 2016-11-30
  • Posts: 2

Topic: WSDL on the basis of XSD

Is XSD the description of several tens the objects connected among themselves, certainly. There is object Request of approximately following structure:

<xsd:complexType name = "RequestType">
<xsd:sequence>
<xsd:element name = "RequestHeader" type = "rht:RequestHeaderType"> </xsd:element>
<xsd:element name = "RequestBody">
<xsd:complexType>
<xsd:sequence>
<xsd:choice>
<xsd:element name = "el1Request" type = "tt1:el1Type"> </xsd:element>
<! - a row of other objects->
<xsd:element name = "el50Request" type = "tt50:el50Type"> </xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

I want to write hands to it WSDL for import in VisualStudio not to describe classes separately and automatically to generate requests / to check answers. Prompt, how it is correct in WSDL to describe request, for example with a request body el50Request? On how many I understand, at first it is necessary to describe the object, type such:

<xsd:complexType name = "el50RequestType" type = "RequestType">
<xsd:sequence>
<xsd:element name = "Request">
<xsd:complexType>
<xsd:sequence>
<xsd:element name = "RequestHeader" type = "rht:RequestHeaderType"> </xsd:element>
<xsd:element name = "RequestBody">
<xsd:complexType>
<xsd:sequence>
<xsd:element name = "el50Request" type = "tt50:el50Type"> </xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

And further already in WSDL to describe a method with request of this type and . With the answer similarly.
But couples  that I above described swears. My object el50RequestType is not pleasant to it, speaks that it does not correspond to type RequestType

2 Reply by Antonariy

  • Antonariy
  • Member
  • Offline
  • Registered: 2008-07-16
  • Posts: 11,491

Re: WSDL on the basis of XSD

WSDL_Guest wrote:

I Want to write hands to it WSDL for import in VisualStudio

absolutely senseless occupation.
All the same it is necessary  a request method, and be typified it should according to the circuit so classes anyway are necessary. Other question that their hands  is not necessary, it is possible to generate from these circuits. And after that the studio itself can generate wsdl.

WSDL_Guest wrote:

But couples  that I above described swears. My object el50RequestType is not pleasant to it, speaks that it does not correspond to type RequestType

To begin with, el50RequestType it is type, and the type does not have attribute type.
Can xsd:element it is necessary was to write?

3 Reply by WSDL_Guest

  • WSDL_Guest
  • New member
  • Offline
  • Registered: 2016-11-30
  • Posts: 2

Re: WSDL on the basis of XSD

Thanks for the answer!
In general it was possible to feed all it to the standard utility xsd.exe and to receive a class.cs on an output, without everyones wsdl
If it is short, the recipe such. We write a script, which renames all xsd into short names (because of restriction in 8 characters in arguments cmd), throws off them in one directory and we launch the utility xsd.exe with parameters where it is enumerated all xsd (0.xsd, 1.xsd...). Communications inside xsd circuits, type import from such that of the directory xsd with such that a name in the utility is ignored, used only that is transferred as arguments to an input xsd.exe