Hi all,

Consider the following snippet of WSDL:

     <xsd:element name="findWellsInputMsg">
       <xsd:complexType>
         <xsd:sequence>
           <xsd:element name="language" type="dds:LanguageType" />
           <xsd:element minOccurs="0" name="longitude"
type="dds:RangeType" />
           <xsd:element minOccurs="0" name="latitude"
type="dds:RangeType" />
           <xsd:element minOccurs="0" name="depth"
type="dds:RangeType" />
           <xsd:element minOccurs="0" maxOccurs="1"
name="hasWaterLevels" type="xsd:boolean" />
           <xsd:element minOccurs="0" maxOccurs="1"
name="hasWellTests" type="xsd:boolean" />
           <xsd:element minOccurs="0" maxOccurs="1" name="hasLogs"
type="xsd:boolean" />
           <xsd:element minOccurs="0" maxOccurs="1"
name="hasAnalysis" type="xsd:boolean" />
         </xsd:sequence>
       </xsd:complexType>
     </xsd:element>

As you see, all parameters are optional except "language".

I import the WSDL in my .NET 3 project through 'Add Service Reference.
I opt to include async operations. Otherwise I leave all options at
their defaults.

Now when I create a request for this operation, it will accept null
for the complex types 'longitude', 'latitude' and 'depth'. These will
then be omitted in the SOAP request generated. But because bools are
not nullable, I can't find a way to leave those out of the request. Is
this a bug in wsdl.exe or am I not seeing something here?

Thanks for your insights,

Martijn van Exel
Software Engineer
http://oegeo.wordpress.com/
-------------------------------------
Geodan S&R
President Kennedylaan 1
1079 MB Amsterdam (NL)
-------------------------------------
Tel: +31 (0)20 - 5711 318
Fax: +31 (0)20 - 5711 333
-------------------------------------
E-mail: martijn.van.exel@geodan.nl
Website: www.geodan.nl
KvK-nummer: 33 247475
Disclaimer: www.geodan.nl/disclaimer
-------------------------------------