|
|
You're in the
dotnet web services
group:Generated proxy WS methods require parameters optional in WSDL
dotnet web services:
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
WCF proxy should be generating your bools with Nullable<bool> or bool?.
Would be interesting to build a service accepting a Nullable<bool> as input and compare the WSDL generated with this one. Tiago Halm [quoted text, click to view] "mvexel" <mvexel@gmail.com> wrote in message news:f78c5c2a-2dbe-495d-98c8-e2ad64680275@s37g2000prg.googlegroups.com... > 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 > -------------------------------------
[quoted text, click to view]
On 19 mrt, 00:48, "Tiago Halm" <th...@nospam.hotmail.com> wrote: > WCF proxy should be generating your bools with Nullable<bool> or bool?. > Would be interesting to build a service accepting a Nullable<bool> as inpu= t > and compare the WSDL generated with this one. > > Tiago Halm > > "mvexel" <mve...@gmail.com> wrote in message > > news:f78c5c2a-2dbe-495d-98c8-e2ad64680275@s37g2000prg.googlegroups.com... > > > > > Hi all, > > > Consider the following snippet of WSDL: > > > =A0 =A0 =A0<xsd:element name=3D"findWellsInputMsg"> > > =A0 =A0 =A0 =A0<xsd:complexType> > > =A0 =A0 =A0 =A0 =A0<xsd:sequence> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element name=3D"language" type=3D"dds:Langua= geType" /> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element minOccurs=3D"0" name=3D"longitude" > > type=3D"dds:RangeType" /> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element minOccurs=3D"0" name=3D"latitude" > > type=3D"dds:RangeType" /> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element minOccurs=3D"0" name=3D"depth" > > type=3D"dds:RangeType" /> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element minOccurs=3D"0" maxOccurs=3D"1" > > name=3D"hasWaterLevels" type=3D"xsd:boolean" /> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element minOccurs=3D"0" maxOccurs=3D"1" > > name=3D"hasWellTests" type=3D"xsd:boolean" /> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element minOccurs=3D"0" maxOccurs=3D"1" name= =3D"hasLogs" > > type=3D"xsd:boolean" /> > > =A0 =A0 =A0 =A0 =A0 =A0<xsd:element minOccurs=3D"0" maxOccurs=3D"1" > > name=3D"hasAnalysis" type=3D"xsd:boolean" /> > > =A0 =A0 =A0 =A0 =A0</xsd:sequence> > > =A0 =A0 =A0 =A0</xsd:complexType> > > =A0 =A0 =A0</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.e...@geodan.nl > > Website:www.geodan.nl > > KvK-nummer: 33 247475 > > Disclaimer:www.geodan.nl/disclaimer > > -------------------------------------- Tekst uit oorspronkelijk bericht = niet weergeven - > > - Tekst uit oorspronkelijk bericht weergeven - My colleague tried that. A service that accepts a bool? (nullable) as input generates a WSDL node with minOccurs=3D"1", maxOccurs=3D"1" and nillable=3D"true". So that's different from the WSDL we got from our service provider, which just provided a boolean with minOccurs=3D"0" maxOccurs=3D"1" and nillable not set. Nu much of a surprise when the test service accepted null input for the boolean just fine. Problem is, I can't control the WSDL I get as it comes from an external provider. They implement their services in Java (JaxWS), I guess I should be asking a JaxWS person why the WSDL turns out like this. Thanks so far! Martijn Martijn van Exel Software Engineer ------------------------------------- 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 -------------------------------------
Seems nillable is missing from System.Web.Services (ASMX, .NET 1.x). See
here: http://kjellsj.blogspot.com/2005/04/optional-numeric-fields-in-infopath.html Have you tried to generate the proxy via "Add Web Reference"? This will make use of .NET 1.x instead of .NET 2.0 (WCF). Tiago Halm [quoted text, click to view] "mvexel" <mvexel@gmail.com> wrote in message news:7c9d335c-955d-4d94-9e32-cf6465371d3d@m34g2000hsc.googlegroups.com... On 19 mrt, 00:48, "Tiago Halm" <th...@nospam.hotmail.com> wrote: > WCF proxy should be generating your bools with Nullable<bool> or bool?. > Would be interesting to build a service accepting a Nullable<bool> as > input > and compare the WSDL generated with this one. > > Tiago Halm > > "mvexel" <mve...@gmail.com> wrote in message > > news:f78c5c2a-2dbe-495d-98c8-e2ad64680275@s37g2000prg.googlegroups.com... > > > > > 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.e...@geodan.nl > > Website:www.geodan.nl > > KvK-nummer: 33 247475 > > Disclaimer:www.geodan.nl/disclaimer > > -------------------------------------- Tekst uit oorspronkelijk bericht > > niet weergeven - > > - Tekst uit oorspronkelijk bericht weergeven - My colleague tried that. A service that accepts a bool? (nullable) as input generates a WSDL node with minOccurs="1", maxOccurs="1" and nillable="true". So that's different from the WSDL we got from our service provider, which just provided a boolean with minOccurs="0" maxOccurs="1" and nillable not set. Nu much of a surprise when the test service accepted null input for the boolean just fine. Problem is, I can't control the WSDL I get as it comes from an external provider. They implement their services in Java (JaxWS), I guess I should be asking a JaxWS person why the WSDL turns out like this. Thanks so far! Martijn Martijn van Exel Software Engineer ------------------------------------- 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 -------------------------------------
[quoted text, click to view]
"Tiago Halm" <thalm@nospam.hotmail.com> wrote in message news:eEFbKfejIHA.5208@TK2MSFTNGP04.phx.gbl... > Seems nillable is missing from System.Web.Services (ASMX, .NET 1.x). See > here: > http://kjellsj.blogspot.com/2005/04/optional-numeric-fields-in-infopath.html > > Have you tried to generate the proxy via "Add Web Reference"? This will > make use of .NET 1.x instead of .NET 2.0 (WCF). Add Web Reference will use ASMX, but for whichever version of .NET you like. In VS2003, .NET 1.1. VS2005, .NET 2.0. In VS2008, .NET 2.0 through 3.5. -- -------------------------------------------------------------------------------- John Saunders | MVP - Windows Server System - Connected System Developer
Yes, "Add Web Reference" will make use of System.Web.Services object model.
This object model is present in both CLR versions available (1.1 and 2.0). Using VS2003 will make use of CLR 1.1 (and .NET 1.1). Using VS2005 (and above, like VS2008) will make use of CLR 2.0 and the respective .NET version (2.0, 3.0, 3.5). However, at build time, you're free to use whatever CLR you choose, 1.1 or 2.0. Tiago Halm [quoted text, click to view] "John Saunders [MVP]" <john.saunders at trizetto.com> wrote in message news:O%23FAYHijIHA.1188@TK2MSFTNGP04.phx.gbl... > "Tiago Halm" <thalm@nospam.hotmail.com> wrote in message > news:eEFbKfejIHA.5208@TK2MSFTNGP04.phx.gbl... >> Seems nillable is missing from System.Web.Services (ASMX, .NET 1.x). See >> here: >> http://kjellsj.blogspot.com/2005/04/optional-numeric-fields-in-infopath.html >> >> Have you tried to generate the proxy via "Add Web Reference"? This will >> make use of .NET 1.x instead of .NET 2.0 (WCF). > > Add Web Reference will use ASMX, but for whichever version of .NET you > like. In VS2003, .NET 1.1. VS2005, .NET 2.0. In VS2008, .NET 2.0 through > 3.5. > -- > -------------------------------------------------------------------------------- > John Saunders | MVP - Windows Server System - Connected System Developer > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |