Sorry for some reason I could not reply to the original thread here:
http://groups.google.com/group/adwords-api/browse_frm/thread/2dbde66de2326e2c?tvc=1
In schema definition, I found that by moving the cardinality rules
onto the sequence element rather than the child, .NET 2.0 and WCF code
generation does not collapse the sequences, and thus does not expose
the bug you have found.
Try
< xsd:complexType name="C">
< xsd:sequence maxOccurs="unbounded" minOccurs="0">
< xsd:element name="someDate" type="xsd:date"/>
< /xsd:sequence>
< /xsd:complexType>
Rather than
< xsd:complexType name="C">
< xsd:sequence>
< xsd:element maxOccurs="unbounded" minOccurs="0" name="someDate"
type="xsd:date"/>
< /xsd:sequence>
< /xsd:complexType>
James
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
