Bug in createXSD

, ,
1

Hi,

I have noticed some strange behaviour in the built-in pub.schema:createXSD service, like in this example :

<xsd:schema>
<xsd:element>
<xsd:element>
<xsd:complextype>
…
</xsd:complextype>
<xsd:complextype>
…
</xsd:complextype>
</xsd:schema>

This has been generated by createXSD for a service that takes two fields as input : a String List and a String. How come can these different field types lead to the 2 same element definitions in the XML schema definition ?

Julien

2

Sorry the XSD did not show up nicely :

<xsd:schema xmlns:xsd=“[url=“XML Schema”]http://www.w3.org/2001/XMLSchema[/url]”>
<xsd:element name=“InputStringList” type=“xsd:string”/>
<xsd:element name=“InputString” type=“xsd:string”/>
<xsd:complexType name=“Input”>
…
</xsd:complexType>
<xsd:complexType name=“Output”>
…
</xsd:complexType>
</xsd:schema>