Controlling WSDL generation for web services.

[Kevin Burton]

I searched some of the documentation and this description of my problem came
closest:

The following original schema element definitions contain minOccurs or
maxOccurs attributes:

<xs:element minOccurs="5" maxOccurs="10" name="Users">
The following code shows the generated Web service code:

public NumberOfUsers[] Users;
When the BizTalk Web Services Publishing Wizard queries the Web service
description, the WSDL type definition is different from the original schema
element definition. When you publish Web services, you lose schema details
including constraints, default values, nillable, and patterns.

The following shows a schema element definition after the wizard queried the
Web service description:

<xs:element minOccurs="0" maxOccurs="unbounded" name="Users">

The problem is that I am not using BizTalk. It may seem to some like I am
starting in the middle (and I am) but the WSDL is auto-generated from the
assemblies that make up the web service. I would like to know if there are
some attribtutes that I can add that would allow me to control the minimum
and maximum size of an array. I would rather the WSDL not indicate that
minOccurs="0" and maxOccurs="unbounded". But if I have an array that is
exactly what the WSDL indicates. I can control the name of the serialized
element and its type. Now I would like to pretend that I have a schema and
control the auto generated WSDL. Any ideas?

Thank you.

Kevin Burton