Support for xsd:list?

[TN]

I have a list like this defined in my wsdl:

<xsd:simpleType name="MyPets">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="dog"/>
<xsd:enumeration value="cat"/>
<xsd:enumeration value="fish"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="PetsList">
<xsd:list itemType="abc:MyPets"/>
</xsd:simpleType>

When I import the wsdl into my .NET project, PetsList is serialized as a
String. Is that the intended behaviour? Or is it simply because xds:list is
not supported?

Thank you,

[Zafar Abbas [MSFT]]

PetsList will be serizlized as a string because the value space of a list
type is a string which contains a list of values corresponding to its
itemType, separated by whitespaces.

So a valid instance of PetsList is "dog cat fish" which is a String of
concatenated values.

"TN" <[e-mail]> wrote in message
news:A8**********************************@microsof t.com...

I have a list like this defined in my wsdl:

<xsd:simpleType name="MyPets">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="dog"/>
<xsd:enumeration value="cat"/>
<xsd:enumeration value="fish"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="PetsList">
<xsd:list itemType="abc:MyPets"/>
</xsd:simpleType>

When I import the wsdl into my .NET project, PetsList is serialized as a
String. Is that the intended behaviour? Or is it simply because xds:list is not supported?

Thank you,

[TN]

Thanks for the response.

Interesting, though. Then I guess, .Net just ignore the constraint (dog,
fish, cat) and allows the application to create a list with arbitrary entries
say "dog chicken cat", even though chicken is clearly an invalid entry
according to the schema.

Thanks,

Tu

"Zafar Abbas [MSFT]" wrote:

PetsList will be serizlized as a string because the value space of a list
type is a string which contains a list of values corresponding to its
itemType, separated by whitespaces.

So a valid instance of PetsList is "dog cat fish" which is a String of
concatenated values.

"TN" <[e-mail]> wrote in message
news:A8**********************************@microsof t.com...

I have a list like this defined in my wsdl:

<xsd:simpleType name="MyPets">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="dog"/>
<xsd:enumeration value="cat"/>
<xsd:enumeration value="fish"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="PetsList">
<xsd:list itemType="abc:MyPets"/>
</xsd:simpleType>

When I import the wsdl into my .NET project, PetsList is serialized as a
String. Is that the intended behaviour? Or is it simply because xds:list

is

not supported?

Thank you,

[Dino Chiesa [Microsoft]]

yes.

"TN" <[e-mail]> wrote in message
news:D9**********************************@microsof t.com...

Thanks for the response.

Interesting, though. Then I guess, .Net just ignore the constraint (dog,
fish, cat) and allows the application to create a list with arbitrary
entries
say "dog chicken cat", even though chicken is clearly an invalid entry
according to the schema.

Thanks,

Tu

"Zafar Abbas [MSFT]" wrote:

PetsList will be serizlized as a string because the value space of a list
type is a string which contains a list of values corresponding to its
itemType, separated by whitespaces.

So a valid instance of PetsList is "dog cat fish" which is a String of
concatenated values.

"TN" <[e-mail]> wrote in message
news:A8**********************************@microsof t.com...

> I have a list like this defined in my wsdl:
>
> <xsd:simpleType name="MyPets">
> <xsd:restriction base="xsd:string">
> <xsd:enumeration value="dog"/>
> <xsd:enumeration value="cat"/>
> <xsd:enumeration value="fish"/>
> </xsd:restriction>
> </xsd:simpleType>
>
> <xsd:simpleType name="PetsList">
> <xsd:list itemType="abc:MyPets"/>
> </xsd:simpleType>
>
> When I import the wsdl into my .NET project, PetsList is serialized as
> a
> String. Is that the intended behaviour? Or is it simply because
> xds:list

is

> not supported?
>
> Thank you,