Web service constants or default values

[Matt D]

I have a bunch of constants used in my web services that the client
also needs to have. Is there a way to declare public properties that
are part of a class or structure as constants or at least give them a
default value through some XML shaping? Thanks.

[Mujtaba Syed]

You can have a separate class in the an ASMX class with static fields. You
could even have an enum if the values are related. WSDL will take care of
creating the correct proxy for the client.

Mujtaba.

"Matt D" <md**********@y ahoo.com> wrote in message
news:sn******** *************** *********@4ax.c om...

I have a bunch of constants used in my web services that the client
also needs to have. Is there a way to declare public properties that
are part of a class or structure as constants or at least give them a
default value through some XML shaping? Thanks.

[Matt D]

Can you give me an example of this? I thought static fields are not
serialized by .NET. Thanks.

On Tue, 14 Dec 2004 14:52:29 -0500, "Mujtaba Syed"
<mu*****@marlab s.com> wrote:

You can have a separate class in the an ASMX class with static fields. You
could even have an enum if the values are related. WSDL will take care of
creating the correct proxy for the client.

Mujtaba.

[erymuzuan]

I would recommend using default value in you WSDL schema type, thoug
some it means hand crafting your WSDL document, but that's should be too
hard, after you 've changed the wSDL generate the server stub(using
/server) and put the implemeation back on this stub

exmaple of Address type having default value for street

<complexType name="Address">
<sequence>
<element name="name" type="string" minOccurs="0"/>
<element name="street" type="string" default="Anystr eet"/>
<element name="city" type="string"/>
</sequence>
</complexType>
Regards
Erymuzuan Mustapa

Matt D wrote:

Can you give me an example of this? I thought static fields are not
serialized by .NET. Thanks.

On Tue, 14 Dec 2004 14:52:29 -0500, "Mujtaba Syed"
<mu*****@marlab s.com> wrote:

You can have a separate class in the an ASMX class with static fields. You
could even have an enum if the values are related. WSDL will take care of
creating the correct proxy for the client.

Mujtaba.

[Anders Norås [MCAD]]

>I have a bunch of constants used in my web services that the client

also needs to have. Is there a way to declare public properties that
are part of a class or structure as constants or at least give them a
default value through some XML shaping? Thanks.

Use an enum to define your constants and declare the properties with this
type. The WSDL will include a definition for your enum. This might also
improve your design since the constants no longer are "magic values", but
something defined strongly typed.

Anders Norås
http://dotnetjunkies.com/weblog/anoras/

[Dan Rogers]

Hi,

Default values happen in a few ways. From a contract basis, your only tool
is XML schema. The schema language does allow one to define default values
for optional fields. In this way, if someone fails to send a field, the
receiving party, when equipped with a schema aware reader, can have the
reader fill in the defaults for them.

In ASP.Net, the reader that is normally used as part of the deserializaiton
process does NOT use the schema (it is an optimized pull-based reader that
was created by looking at the schema at one point). Thus, the default
behavior for serialized classes (perhaps created with XSD.exe or
XmlObjectGen.ex e) does NOT apply defaults.

To change this, you have a few options. First, you can pass the XML as
received thru a validating reader before it is processed by the default XML
serializer. This is easy enough to do and you can use the Web Service
Extension mechanism to accomplish this. In this way you alter the received
XML before ASP.net deserializes it. If you use a validating reader and
preloaded schema cache, the defaults will be added for you - and you pass
the altered XML stream on to the default serializer.

Another way to do this is to change your constructors (in both the server
side class and any proxy logic generated by add-web-reference) so that the
values you want to see are there, so that if an optional element or
attribute wasn't present when serialized (or on class_new), the default
values are available.

I hope this helps

Dan Rogers
Microsoft Corporation
--------------------
NNTP-Posting-Date: Tue, 14 Dec 2004 13:20:26 -0600
From: Matt D <md**********@y ahoo.com>
Newsgroups: microsoft.publi c.dotnet.framew ork.webservices
Subject: Web service constants or default values
Date: Tue, 14 Dec 2004 12:20:25 -0700
Message-ID: <sn************ *************** *****@4ax.com>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 4
X-Trace:
sv3-S6UH2Evz25Y1XwE HtNs65ctZsXbT+l t3eqkVAgil7oli/WFQMWQ6gi9a1O3s ry7W3jOWwOtr
gertlew!aNb3FbN Yksqs8tAK/Uiw1F79fNkf+e4X jpxPDl+O488vUPU GtQwzGuPplvrsio CnRD7+
X-Complaints-To: ab***@giganews. com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your
complaint properly
X-Postfilter: 1.3.20
Path:
cpmsftngxa10.ph x.gbl!TK2MSFTNG XA01.phx.gbl!cp msftngxa06.phx. gbl!TK2MSFTNGP0 8
.phx.gbl!newsfe ed00.sul.t-online.de!t-online.de!borde r2.nntp.dca.gig anews.co
m!border1.nntp. dca.giganews.co m!nntp.giganews .com!local1.nnt p.dca.giganews. c
om!news.giganew s.com.POSTED!no t-for-mail
Xref: cpmsftngxa10.ph x.gbl
microsoft.publi c.dotnet.framew ork.webservices :8080
X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.webservices

I have a bunch of constants used in my web services that the client
also needs to have. Is there a way to declare public properties that
are part of a class or structure as constants or at least give them a
default value through some XML shaping? Thanks.