Re: Still more, Re: IWS problems

Pargraph 5 of this article describes the use of the "specified" fields in a .NET web service client:

http://thecodemonk.com/2009/04/27/first-usage-of-wcf-and-specified-fields/

Since the article indicates that "specified" is used to indicate that a null value was passed, does your web service emit nulls for any of the numeric fields? If so, your customer should test the fields for a null value before trying to access the fields as numerics.

Craig Pelkie

----- Original Message ----- From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, October 21, 2010 10:09 AM
Subject: Still more, Re: IWS problems

James H. H. Lampert wrote:

2. For all of the parameters specified as "decimal," they're also
finding a "specified" field associated with the parameter. Anybody have
the slightest idea what that's about?

Example of above (from the customer, from before we tried eliminating
the decimal points):

Name Value
wsQuotationHeaderInput {...}
_P01205 0D
_P01205Specified True
_P01206 20100616D
_P01206Specified True
. . .
_P01213 "ATP Quotation"
_P01214 "Pending"
_P01215 44466.89D
_P01215Specified True
. . . and so forth . . .

Notice that only the decimal parameters have "Specified" fields attached
to them. Any idea what they are?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.