|
|
You're in the
dotnet web services
group:How to tell if a string element is null or really null?
dotnet web services:
if( IsNullOrEmpty(person.lastname) ) // Echo Is null else // Echo Is not null That is only valid for string types. For other kind of reference type, you should check if it is equal to null. if( person.lastname == null) // Echo Is null else // Echo Is not null [quoted text, click to view] "Jiho Han" <jihohan@yahoo.com> wrote in message news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... > Here's the issue. > > You have a class, > > Class Person > { > public int id; > public string firstname; > public string lastname; > } > > when you expose it via webservice, > > [WebMethod] > public void UpdatePerson(Person) > { > ... > } > > How do I know whether a field value has been specified or not? For value > types, there is that matching XXXXSpecified buddy field, but for string > type, there doesn't seem to be one. > So if incoming Xml looks something like this: > <Person> > <firstname>Jiho</firstname> > </Person> > > when deserialized into a Person object, lastname field will contain null, > which doesn't tell me whether the field is simply missing (thus safely > ignored) or lastname field should be set to null (in the database, for > example). > > Any idea how to go about this? > Thanks in advance. > > > Jiho Han > Senior Software Engineer > Infinity Info Systems > The Sales Technology Experts > Tel: 212.563.4400 x216 > Fax: 212.760.0540 > jhan@infinityinfo.com > www.infinityinfo.com > >
Here's the issue.
You have a class, Class Person { public int id; public string firstname; public string lastname; } when you expose it via webservice, [WebMethod] public void UpdatePerson(Person) { ... } How do I know whether a field value has been specified or not? For value types, there is that matching XXXXSpecified buddy field, but for string type, there doesn't seem to be one. So if incoming Xml looks something like this: <Person> <firstname>Jiho</firstname> </Person> when deserialized into a Person object, lastname field will contain null, which doesn't tell me whether the field is simply missing (thus safely ignored) or lastname field should be set to null (in the database, for example). Any idea how to go about this? Thanks in advance. Jiho Han Senior Software Engineer Infinity Info Systems The Sales Technology Experts Tel: 212.563.4400 x216 Fax: 212.760.0540 jhan@infinityinfo.com www.infinityinfo.com
Pablo,
Perhaps, it is more of a design question... If you want a field to be set to null (think database), how would you specify that from the client side? If you don't include the field, it's null on the server. If you set it to null, it's still null on the server. My point is that there seems to be no way of knowing whether the client intended a field to be set to null vs. skip the field for processing becasue it's missing from the xml. i.e.) <Person> <Lastname>Han</Lastname> <Firstname/> </Person> and <Person> <Lastname>Han</Lastname> </Person> deserializes into an identical object state. [quoted text, click to view] > It is as simple as this, > > if( IsNullOrEmpty(person.lastname) ) > // Echo Is null > else > // Echo Is not null > That is only valid for string types. For other kind of reference type, > you should check if it is equal to null. > > if( person.lastname == null) > // Echo Is null > else > // Echo Is not null > "Jiho Han" <jihohan@yahoo.com> wrote in message > news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... > >> Here's the issue. >> >> You have a class, >> >> Class Person >> { >> public int id; >> public string firstname; >> public string lastname; >> } >> when you expose it via webservice, >> >> [WebMethod] >> public void UpdatePerson(Person) >> { >> ... >> } >> How do I know whether a field value has been specified or not? For >> value >> types, there is that matching XXXXSpecified buddy field, but for >> string >> type, there doesn't seem to be one. >> So if incoming Xml looks something like this: >> <Person> >> <firstname>Jiho</firstname> >> </Person> >> when deserialized into a Person object, lastname field will contain >> null, which doesn't tell me whether the field is simply missing (thus >> safely ignored) or lastname field should be set to null (in the >> database, for example). >> >> Any idea how to go about this? >> Thanks in advance. >> Jiho Han >> Senior Software Engineer >> Infinity Info Systems >> The Sales Technology Experts >> Tel: 212.563.4400 x216 >> Fax: 212.760.0540 >> jhan@infinityinfo.com >> www.infinityinfo.com
An XML document, and in particular, a SOAP document, is not quite as simple
as you seem to think. It can indicate whether the value is null or not. Example: <SomeObject xsi:nil="true" /> -- HTH, Kevin Spencer Microsoft MVP Professional Chicken Salad Alchemist Sequence, Selection, Iteration. [quoted text, click to view] "Jiho Han" <jihohan@yahoo.com> wrote in message news:a19ab9b61b8908c87d39dd555e26@msnews.microsoft.com... > Pablo, > > Perhaps, it is more of a design question... > > If you want a field to be set to null (think database), how would you > specify that from the client side? > If you don't include the field, it's null on the server. If you set it to > null, it's still null on the server. > My point is that there seems to be no way of knowing whether the client > intended a field to be set to null vs. skip the field for processing > becasue it's missing from the xml. > i.e.) > <Person> > <Lastname>Han</Lastname> > <Firstname/> > </Person> > > and > <Person> > <Lastname>Han</Lastname> > </Person> > > deserializes into an identical object state. > >> It is as simple as this, >> >> if( IsNullOrEmpty(person.lastname) ) >> // Echo Is null >> else >> // Echo Is not null >> That is only valid for string types. For other kind of reference type, >> you should check if it is equal to null. >> >> if( person.lastname == null) >> // Echo Is null >> else >> // Echo Is not null >> "Jiho Han" <jihohan@yahoo.com> wrote in message >> news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... >> >>> Here's the issue. >>> >>> You have a class, >>> >>> Class Person >>> { >>> public int id; >>> public string firstname; >>> public string lastname; >>> } >>> when you expose it via webservice, >>> >>> [WebMethod] >>> public void UpdatePerson(Person) >>> { >>> ... >>> } >>> How do I know whether a field value has been specified or not? For >>> value >>> types, there is that matching XXXXSpecified buddy field, but for >>> string >>> type, there doesn't seem to be one. >>> So if incoming Xml looks something like this: >>> <Person> >>> <firstname>Jiho</firstname> >>> </Person> >>> when deserialized into a Person object, lastname field will contain >>> null, which doesn't tell me whether the field is simply missing (thus >>> safely ignored) or lastname field should be set to null (in the >>> database, for example). >>> >>> Any idea how to go about this? >>> Thanks in advance. >>> Jiho Han >>> Senior Software Engineer >>> Infinity Info Systems >>> The Sales Technology Experts >>> Tel: 212.563.4400 x216 >>> Fax: 212.760.0540 >>> jhan@infinityinfo.com >>> www.infinityinfo.com > >
Kevin,
I understand that the xml received by the soap endpoint is different. However, when the xml document is deserialized into an object, there is no difference - or rather I don't know of a way - between: <Person> <Lastname xsi:nil = "true"/> </Person> vs. <Person> </Person> When it gets deserialized into an object, Person person = <from soap response> person.Lastname == null // true for both! If there is a way to tell the difference, that'd be great. Is there some kind of a hook into the soap deserialization scheme? [quoted text, click to view] > An XML document, and in particular, a SOAP document, is not quite as > simple as you seem to think. It can indicate whether the value is null > or not. Example: > > <SomeObject xsi:nil="true" /> > > Kevin Spencer > Microsoft MVP > Professional Chicken Salad Alchemist > Sequence, Selection, Iteration. > > "Jiho Han" <jihohan@yahoo.com> wrote in message > news:a19ab9b61b8908c87d39dd555e26@msnews.microsoft.com... > >> Pablo, >> >> Perhaps, it is more of a design question... >> >> If you want a field to be set to null (think database), how would you >> specify that from the client side? >> If you don't include the field, it's null on the server. If you set >> it to >> null, it's still null on the server. >> My point is that there seems to be no way of knowing whether the >> client >> intended a field to be set to null vs. skip the field for processing >> becasue it's missing from the xml. >> i.e.) >> <Person> >> <Lastname>Han</Lastname> >> <Firstname/> >> </Person> >> and >> <Person> >> <Lastname>Han</Lastname> >> </Person> >> deserializes into an identical object state. >> >>> It is as simple as this, >>> >>> if( IsNullOrEmpty(person.lastname) ) >>> // Echo Is null >>> else >>> // Echo Is not null >>> That is only valid for string types. For other kind of reference >>> type, >>> you should check if it is equal to null. >>> if( person.lastname == null) >>> // Echo Is null >>> else >>> // Echo Is not null >>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>> news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... >>>> Here's the issue. >>>> >>>> You have a class, >>>> >>>> Class Person >>>> { >>>> public int id; >>>> public string firstname; >>>> public string lastname; >>>> } >>>> when you expose it via webservice, >>>> [WebMethod] >>>> public void UpdatePerson(Person) >>>> { >>>> ... >>>> } >>>> How do I know whether a field value has been specified or not? For >>>> value >>>> types, there is that matching XXXXSpecified buddy field, but for >>>> string >>>> type, there doesn't seem to be one. >>>> So if incoming Xml looks something like this: >>>> <Person> >>>> <firstname>Jiho</firstname> >>>> </Person> >>>> when deserialized into a Person object, lastname field will contain >>>> null, which doesn't tell me whether the field is simply missing >>>> (thus >>>> safely ignored) or lastname field should be set to null (in the >>>> database, for example). >>>> Any idea how to go about this? >>>> Thanks in advance. >>>> Jiho Han >>>> Senior Software Engineer >>>> Infinity Info Systems >>>> The Sales Technology Experts >>>> Tel: 212.563.4400 x216 >>>> Fax: 212.760.0540 >>>> jhan@infinityinfo.com >>>> www.infinityinfo.com
I haven't personally encountered this situation. However, I think that
applying some custom formatting to the SOAP XSD might do the trick. See http://msdn2.microsoft.com/en-us/library/k1y9z356.aspx -- HTH, Kevin Spencer Microsoft MVP Professional Chicken Salad Alchemist Sequence, Selection, Iteration. [quoted text, click to view] "Jiho Han" <jihohan@yahoo.com> wrote in message news:a19ab9b61ba658c87ddbf521dbd8@msnews.microsoft.com... > Kevin, > > I understand that the xml received by the soap endpoint is different. > However, when the xml document is deserialized into an object, there is no > difference - or rather I don't know of a way - between: > > <Person> > <Lastname xsi:nil = "true"/> > </Person> > > vs. > > <Person> > </Person> > > When it gets deserialized into an object, > > Person person = <from soap response> > person.Lastname == null // true for both! > > If there is a way to tell the difference, that'd be great. Is there some > kind of a hook into the soap deserialization scheme? >> An XML document, and in particular, a SOAP document, is not quite as >> simple as you seem to think. It can indicate whether the value is null >> or not. Example: >> >> <SomeObject xsi:nil="true" /> >> >> Kevin Spencer >> Microsoft MVP >> Professional Chicken Salad Alchemist >> Sequence, Selection, Iteration. >> >> "Jiho Han" <jihohan@yahoo.com> wrote in message >> news:a19ab9b61b8908c87d39dd555e26@msnews.microsoft.com... >> >>> Pablo, >>> >>> Perhaps, it is more of a design question... >>> >>> If you want a field to be set to null (think database), how would you >>> specify that from the client side? >>> If you don't include the field, it's null on the server. If you set >>> it to >>> null, it's still null on the server. >>> My point is that there seems to be no way of knowing whether the >>> client >>> intended a field to be set to null vs. skip the field for processing >>> becasue it's missing from the xml. >>> i.e.) >>> <Person> >>> <Lastname>Han</Lastname> >>> <Firstname/> >>> </Person> >>> and >>> <Person> >>> <Lastname>Han</Lastname> >>> </Person> >>> deserializes into an identical object state. >>> >>>> It is as simple as this, >>>> >>>> if( IsNullOrEmpty(person.lastname) ) >>>> // Echo Is null >>>> else >>>> // Echo Is not null >>>> That is only valid for string types. For other kind of reference >>>> type, >>>> you should check if it is equal to null. >>>> if( person.lastname == null) >>>> // Echo Is null >>>> else >>>> // Echo Is not null >>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>> news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... >>>>> Here's the issue. >>>>> >>>>> You have a class, >>>>> >>>>> Class Person >>>>> { >>>>> public int id; >>>>> public string firstname; >>>>> public string lastname; >>>>> } >>>>> when you expose it via webservice, >>>>> [WebMethod] >>>>> public void UpdatePerson(Person) >>>>> { >>>>> ... >>>>> } >>>>> How do I know whether a field value has been specified or not? For >>>>> value >>>>> types, there is that matching XXXXSpecified buddy field, but for >>>>> string >>>>> type, there doesn't seem to be one. >>>>> So if incoming Xml looks something like this: >>>>> <Person> >>>>> <firstname>Jiho</firstname> >>>>> </Person> >>>>> when deserialized into a Person object, lastname field will contain >>>>> null, which doesn't tell me whether the field is simply missing >>>>> (thus >>>>> safely ignored) or lastname field should be set to null (in the >>>>> database, for example). >>>>> Any idea how to go about this? >>>>> Thanks in advance. >>>>> Jiho Han >>>>> Senior Software Engineer >>>>> Infinity Info Systems >>>>> The Sales Technology Experts >>>>> Tel: 212.563.4400 x216 >>>>> Fax: 212.760.0540 >>>>> jhan@infinityinfo.com >>>>> www.infinityinfo.com > >
Hello Kevin,
I am not exactly sure that will help. It doesn't seem to matter how the SOAP is formatted, the end result is that when the XmlSerializer consumes an incoming xml, it's same. Once in object form, there is no way to tell which format it came in. This is a bit frustrating. Thanks for your help though. Jiho [quoted text, click to view] > I haven't personally encountered this situation. However, I think that > applying some custom formatting to the SOAP XSD might do the trick. > See http://msdn2.microsoft.com/en-us/library/k1y9z356.aspx > > Kevin Spencer > Microsoft MVP > Professional Chicken Salad Alchemist > Sequence, Selection, Iteration. > > "Jiho Han" <jihohan@yahoo.com> wrote in message > news:a19ab9b61ba658c87ddbf521dbd8@msnews.microsoft.com... > >> Kevin, >> >> I understand that the xml received by the soap endpoint is different. >> However, when the xml document is deserialized into an object, there >> is no difference - or rather I don't know of a way - between: >> >> <Person> >> <Lastname xsi:nil = "true"/> >> </Person> >> vs. >> >> <Person> >> </Person> >> When it gets deserialized into an object, >> >> Person person = <from soap response> >> person.Lastname == null // true for both! >> If there is a way to tell the difference, that'd be great. Is there >> some kind of a hook into the soap deserialization scheme? >> >>> An XML document, and in particular, a SOAP document, is not quite as >>> simple as you seem to think. It can indicate whether the value is >>> null or not. Example: >>> >>> <SomeObject xsi:nil="true" /> >>> >>> Kevin Spencer >>> Microsoft MVP >>> Professional Chicken Salad Alchemist >>> Sequence, Selection, Iteration. >>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>> news:a19ab9b61b8908c87d39dd555e26@msnews.microsoft.com... >>>> Pablo, >>>> >>>> Perhaps, it is more of a design question... >>>> >>>> If you want a field to be set to null (think database), how would >>>> you >>>> specify that from the client side? >>>> If you don't include the field, it's null on the server. If you >>>> set >>>> it to >>>> null, it's still null on the server. >>>> My point is that there seems to be no way of knowing whether the >>>> client >>>> intended a field to be set to null vs. skip the field for >>>> processing >>>> becasue it's missing from the xml. >>>> i.e.) >>>> <Person> >>>> <Lastname>Han</Lastname> >>>> <Firstname/> >>>> </Person> >>>> and >>>> <Person> >>>> <Lastname>Han</Lastname> >>>> </Person> >>>> deserializes into an identical object state. >>>>> It is as simple as this, >>>>> >>>>> if( IsNullOrEmpty(person.lastname) ) >>>>> // Echo Is null >>>>> else >>>>> // Echo Is not null >>>>> That is only valid for string types. For other kind of reference >>>>> type, >>>>> you should check if it is equal to null. >>>>> if( person.lastname == null) >>>>> // Echo Is null >>>>> else >>>>> // Echo Is not null >>>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>>> news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... >>>>>> Here's the issue. >>>>>> >>>>>> You have a class, >>>>>> >>>>>> Class Person >>>>>> { >>>>>> public int id; >>>>>> public string firstname; >>>>>> public string lastname; >>>>>> } >>>>>> when you expose it via webservice, >>>>>> [WebMethod] >>>>>> public void UpdatePerson(Person) >>>>>> { >>>>>> ... >>>>>> } >>>>>> How do I know whether a field value has been specified or not? >>>>>> For >>>>>> value >>>>>> types, there is that matching XXXXSpecified buddy field, but for >>>>>> string >>>>>> type, there doesn't seem to be one. >>>>>> So if incoming Xml looks something like this: >>>>>> <Person> >>>>>> <firstname>Jiho</firstname> >>>>>> </Person> >>>>>> when deserialized into a Person object, lastname field will >>>>>> contain >>>>>> null, which doesn't tell me whether the field is simply missing >>>>>> (thus >>>>>> safely ignored) or lastname field should be set to null (in the >>>>>> database, for example). >>>>>> Any idea how to go about this? >>>>>> Thanks in advance. >>>>>> Jiho Han >>>>>> Senior Software Engineer >>>>>> Infinity Info Systems >>>>>> The Sales Technology Experts >>>>>> Tel: 212.563.4400 x216 >>>>>> Fax: 212.760.0540 >>>>>> jhan@infinityinfo.com >>>>>> www.infinityinfo.com
Is there a difference between the two in the XML InfoSet model?
John [quoted text, click to view] "Jiho Han" <jihohan@yahoo.com> wrote in message news:a19ab9b61bad38c87e27a332ada9@msnews.microsoft.com... > Hello Kevin, > > I am not exactly sure that will help. It doesn't seem to matter how the > SOAP is formatted, the end result is that when the XmlSerializer consumes > an incoming xml, it's same. Once in object form, there is no way to tell > which format it came in. > This is a bit frustrating. Thanks for your help though. > > Jiho > >> I haven't personally encountered this situation. However, I think that >> applying some custom formatting to the SOAP XSD might do the trick. >> See http://msdn2.microsoft.com/en-us/library/k1y9z356.aspx >> >> Kevin Spencer >> Microsoft MVP >> Professional Chicken Salad Alchemist >> Sequence, Selection, Iteration. >> >> "Jiho Han" <jihohan@yahoo.com> wrote in message >> news:a19ab9b61ba658c87ddbf521dbd8@msnews.microsoft.com... >> >>> Kevin, >>> >>> I understand that the xml received by the soap endpoint is different. >>> However, when the xml document is deserialized into an object, there >>> is no difference - or rather I don't know of a way - between: >>> >>> <Person> >>> <Lastname xsi:nil = "true"/> >>> </Person> >>> vs. >>> >>> <Person> >>> </Person> >>> When it gets deserialized into an object, >>> >>> Person person = <from soap response> >>> person.Lastname == null // true for both! >>> If there is a way to tell the difference, that'd be great. Is there >>> some kind of a hook into the soap deserialization scheme? >>> >>>> An XML document, and in particular, a SOAP document, is not quite as >>>> simple as you seem to think. It can indicate whether the value is >>>> null or not. Example: >>>> >>>> <SomeObject xsi:nil="true" /> >>>> >>>> Kevin Spencer >>>> Microsoft MVP >>>> Professional Chicken Salad Alchemist >>>> Sequence, Selection, Iteration. >>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>> news:a19ab9b61b8908c87d39dd555e26@msnews.microsoft.com... >>>>> Pablo, >>>>> >>>>> Perhaps, it is more of a design question... >>>>> >>>>> If you want a field to be set to null (think database), how would >>>>> you >>>>> specify that from the client side? >>>>> If you don't include the field, it's null on the server. If you >>>>> set >>>>> it to >>>>> null, it's still null on the server. >>>>> My point is that there seems to be no way of knowing whether the >>>>> client >>>>> intended a field to be set to null vs. skip the field for >>>>> processing >>>>> becasue it's missing from the xml. >>>>> i.e.) >>>>> <Person> >>>>> <Lastname>Han</Lastname> >>>>> <Firstname/> >>>>> </Person> >>>>> and >>>>> <Person> >>>>> <Lastname>Han</Lastname> >>>>> </Person> >>>>> deserializes into an identical object state. >>>>>> It is as simple as this, >>>>>> >>>>>> if( IsNullOrEmpty(person.lastname) ) >>>>>> // Echo Is null >>>>>> else >>>>>> // Echo Is not null >>>>>> That is only valid for string types. For other kind of reference >>>>>> type, >>>>>> you should check if it is equal to null. >>>>>> if( person.lastname == null) >>>>>> // Echo Is null >>>>>> else >>>>>> // Echo Is not null >>>>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>>>> news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... >>>>>>> Here's the issue. >>>>>>> >>>>>>> You have a class, >>>>>>> >>>>>>> Class Person >>>>>>> { >>>>>>> public int id; >>>>>>> public string firstname; >>>>>>> public string lastname; >>>>>>> } >>>>>>> when you expose it via webservice, >>>>>>> [WebMethod] >>>>>>> public void UpdatePerson(Person) >>>>>>> { >>>>>>> ... >>>>>>> } >>>>>>> How do I know whether a field value has been specified or not? >>>>>>> For >>>>>>> value >>>>>>> types, there is that matching XXXXSpecified buddy field, but for >>>>>>> string >>>>>>> type, there doesn't seem to be one. >>>>>>> So if incoming Xml looks something like this: >>>>>>> <Person> >>>>>>> <firstname>Jiho</firstname> >>>>>>> </Person> >>>>>>> when deserialized into a Person object, lastname field will >>>>>>> contain >>>>>>> null, which doesn't tell me whether the field is simply missing >>>>>>> (thus >>>>>>> safely ignored) or lastname field should be set to null (in the >>>>>>> database, for example). >>>>>>> Any idea how to go about this? >>>>>>> Thanks in advance. >>>>>>> Jiho Han >>>>>>> Senior Software Engineer >>>>>>> Infinity Info Systems >>>>>>> The Sales Technology Experts >>>>>>> Tel: 212.563.4400 x216 >>>>>>> Fax: 212.760.0540 >>>>>>> jhan@infinityinfo.com >>>>>>> www.infinityinfo.com > >
John,
I don't know, you tell me, are these two different? <Person> <FirstName xsi:nil = "true" /> <Person> <Person> </Person> Thanks [quoted text, click to view] > Is there a difference between the two in the XML InfoSet model? > > John > > "Jiho Han" <jihohan@yahoo.com> wrote in message > news:a19ab9b61bad38c87e27a332ada9@msnews.microsoft.com... > >> Hello Kevin, >> >> I am not exactly sure that will help. It doesn't seem to matter how >> the >> SOAP is formatted, the end result is that when the XmlSerializer >> consumes >> an incoming xml, it's same. Once in object form, there is no way to >> tell >> which format it came in. >> This is a bit frustrating. Thanks for your help though. >> Jiho >> >>> I haven't personally encountered this situation. However, I think >>> that applying some custom formatting to the SOAP XSD might do the >>> trick. See http://msdn2.microsoft.com/en-us/library/k1y9z356.aspx >>> >>> Kevin Spencer >>> Microsoft MVP >>> Professional Chicken Salad Alchemist >>> Sequence, Selection, Iteration. >>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>> news:a19ab9b61ba658c87ddbf521dbd8@msnews.microsoft.com... >>>> Kevin, >>>> >>>> I understand that the xml received by the soap endpoint is >>>> different. However, when the xml document is deserialized into an >>>> object, there is no difference - or rather I don't know of a way - >>>> between: >>>> >>>> <Person> >>>> <Lastname xsi:nil = "true"/> >>>> </Person> >>>> vs. >>>> <Person> >>>> </Person> >>>> When it gets deserialized into an object, >>>> Person person = <from soap response> >>>> person.Lastname == null // true for both! >>>> If there is a way to tell the difference, that'd be great. Is >>>> there >>>> some kind of a hook into the soap deserialization scheme? >>>>> An XML document, and in particular, a SOAP document, is not quite >>>>> as simple as you seem to think. It can indicate whether the value >>>>> is null or not. Example: >>>>> >>>>> <SomeObject xsi:nil="true" /> >>>>> >>>>> Kevin Spencer >>>>> Microsoft MVP >>>>> Professional Chicken Salad Alchemist >>>>> Sequence, Selection, Iteration. >>>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>>> news:a19ab9b61b8908c87d39dd555e26@msnews.microsoft.com... >>>>>> Pablo, >>>>>> >>>>>> Perhaps, it is more of a design question... >>>>>> >>>>>> If you want a field to be set to null (think database), how would >>>>>> you >>>>>> specify that from the client side? >>>>>> If you don't include the field, it's null on the server. If you >>>>>> set >>>>>> it to >>>>>> null, it's still null on the server. >>>>>> My point is that there seems to be no way of knowing whether the >>>>>> client >>>>>> intended a field to be set to null vs. skip the field for >>>>>> processing >>>>>> becasue it's missing from the xml. >>>>>> i.e.) >>>>>> <Person> >>>>>> <Lastname>Han</Lastname> >>>>>> <Firstname/> >>>>>> </Person> >>>>>> and >>>>>> <Person> >>>>>> <Lastname>Han</Lastname> >>>>>> </Person> >>>>>> deserializes into an identical object state. >>>>>>> It is as simple as this, >>>>>>> >>>>>>> if( IsNullOrEmpty(person.lastname) ) >>>>>>> // Echo Is null >>>>>>> else >>>>>>> // Echo Is not null >>>>>>> That is only valid for string types. For other kind of reference >>>>>>> type, >>>>>>> you should check if it is equal to null. >>>>>>> if( person.lastname == null) >>>>>>> // Echo Is null >>>>>>> else >>>>>>> // Echo Is not null >>>>>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>>>>> news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... >>>>>>>> Here's the issue. >>>>>>>> >>>>>>>> You have a class, >>>>>>>> >>>>>>>> Class Person >>>>>>>> { >>>>>>>> public int id; >>>>>>>> public string firstname; >>>>>>>> public string lastname; >>>>>>>> } >>>>>>>> when you expose it via webservice, >>>>>>>> [WebMethod] >>>>>>>> public void UpdatePerson(Person) >>>>>>>> { >>>>>>>> ... >>>>>>>> } >>>>>>>> How do I know whether a field value has been specified or not? >>>>>>>> For >>>>>>>> value >>>>>>>> types, there is that matching XXXXSpecified buddy field, but >>>>>>>> for >>>>>>>> string >>>>>>>> type, there doesn't seem to be one. >>>>>>>> So if incoming Xml looks something like this: >>>>>>>> <Person> >>>>>>>> <firstname>Jiho</firstname> >>>>>>>> </Person> >>>>>>>> when deserialized into a Person object, lastname field will >>>>>>>> contain >>>>>>>> null, which doesn't tell me whether the field is simply missing >>>>>>>> (thus >>>>>>>> safely ignored) or lastname field should be set to null (in the >>>>>>>> database, for example). >>>>>>>> Any idea how to go about this? >>>>>>>> Thanks in advance. >>>>>>>> Jiho Han >>>>>>>> Senior Software Engineer >>>>>>>> Infinity Info Systems >>>>>>>> The Sales Technology Experts >>>>>>>> Tel: 212.563.4400 x216 >>>>>>>> Fax: 212.760.0540 >>>>>>>> jhan@infinityinfo.com >>>>>>>> www.infinityinfo.com
(Answering my own question) from the w3c rec,
2.6.2 xsi:nil XML Schema: Structures introduces a mechanism for signaling that an element should be accepted as ·valid· when it has no content despite a content type which does not require or even necessarily allow empty content. An element may be ·valid· without content if it has the attribute xsi:nil with the value true. An element so labeled must be empty, but can carry attributes if permitted by the corresponding complex type. which tells me, "nillability" is strictly about the content of an element. So in that case, a missing optional element vs. a nillable element which possibly can carry attributes, are different. btw, in my schema, FirstName would be defined this ways: <xs:element name="FirstName" minOccurs="0" nillable="true"/> Thanks Jiho [quoted text, click to view] > John, > > I don't know, you tell me, are these two different? > > <Person> > <FirstName xsi:nil = "true" /> > <Person> > <Person> > </Person> > Thanks > >> Is there a difference between the two in the XML InfoSet model? >> >> John >> >> "Jiho Han" <jihohan@yahoo.com> wrote in message >> news:a19ab9b61bad38c87e27a332ada9@msnews.microsoft.com... >>> Hello Kevin, >>> >>> I am not exactly sure that will help. It doesn't seem to matter how >>> the >>> SOAP is formatted, the end result is that when the XmlSerializer >>> consumes >>> an incoming xml, it's same. Once in object form, there is no way to >>> tell >>> which format it came in. >>> This is a bit frustrating. Thanks for your help though. >>> Jiho >>>> I haven't personally encountered this situation. However, I think >>>> that applying some custom formatting to the SOAP XSD might do the >>>> trick. See http://msdn2.microsoft.com/en-us/library/k1y9z356.aspx >>>> >>>> Kevin Spencer >>>> Microsoft MVP >>>> Professional Chicken Salad Alchemist >>>> Sequence, Selection, Iteration. >>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>> news:a19ab9b61ba658c87ddbf521dbd8@msnews.microsoft.com... >>>>> Kevin, >>>>> >>>>> I understand that the xml received by the soap endpoint is >>>>> different. However, when the xml document is deserialized into an >>>>> object, there is no difference - or rather I don't know of a way - >>>>> between: >>>>> >>>>> <Person> >>>>> <Lastname xsi:nil = "true"/> >>>>> </Person> >>>>> vs. >>>>> <Person> >>>>> </Person> >>>>> When it gets deserialized into an object, >>>>> Person person = <from soap response> >>>>> person.Lastname == null // true for both! >>>>> If there is a way to tell the difference, that'd be great. Is >>>>> there >>>>> some kind of a hook into the soap deserialization scheme? >>>>>> An XML document, and in particular, a SOAP document, is not quite >>>>>> as simple as you seem to think. It can indicate whether the value >>>>>> is null or not. Example: >>>>>> >>>>>> <SomeObject xsi:nil="true" /> >>>>>> >>>>>> Kevin Spencer >>>>>> Microsoft MVP >>>>>> Professional Chicken Salad Alchemist >>>>>> Sequence, Selection, Iteration. >>>>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>>>> news:a19ab9b61b8908c87d39dd555e26@msnews.microsoft.com... >>>>>>> Pablo, >>>>>>> >>>>>>> Perhaps, it is more of a design question... >>>>>>> >>>>>>> If you want a field to be set to null (think database), how >>>>>>> would >>>>>>> you >>>>>>> specify that from the client side? >>>>>>> If you don't include the field, it's null on the server. If you >>>>>>> set >>>>>>> it to >>>>>>> null, it's still null on the server. >>>>>>> My point is that there seems to be no way of knowing whether the >>>>>>> client >>>>>>> intended a field to be set to null vs. skip the field for >>>>>>> processing >>>>>>> becasue it's missing from the xml. >>>>>>> i.e.) >>>>>>> <Person> >>>>>>> <Lastname>Han</Lastname> >>>>>>> <Firstname/> >>>>>>> </Person> >>>>>>> and >>>>>>> <Person> >>>>>>> <Lastname>Han</Lastname> >>>>>>> </Person> >>>>>>> deserializes into an identical object state. >>>>>>>> It is as simple as this, >>>>>>>> >>>>>>>> if( IsNullOrEmpty(person.lastname) ) >>>>>>>> // Echo Is null >>>>>>>> else >>>>>>>> // Echo Is not null >>>>>>>> That is only valid for string types. For other kind of >>>>>>>> reference >>>>>>>> type, >>>>>>>> you should check if it is equal to null. >>>>>>>> if( person.lastname == null) >>>>>>>> // Echo Is null >>>>>>>> else >>>>>>>> // Echo Is not null >>>>>>>> "Jiho Han" <jihohan@yahoo.com> wrote in message >>>>>>>> news:a19ab9b61a8548c87d1389027fb1@msnews.microsoft.com... >>>>>>>>> Here's the issue. >>>>>>>>> >>>>>>>>> You have a class, >>>>>>>>> >>>>>>>>> Class Person >>>>>>>>> { >>>>>>>>> public int id; >>>>>>>>> public string firstname; >>>>>>>>> public string lastname; >>>>>>>>> } >>>>>>>>> when you expose it via webservice, >>>>>>>>> [WebMethod] >>>>>>>>> public void UpdatePerson(Person) >>>>>>>>> { >>>>>>>>> ... >>>>>>>>> } >>>>>>>>> How do I know whether a field value has been specified or not? >>>>>>>>> For >>>>>>>>> value >>>>>>>>> types, there is that matching XXXXSpecified buddy field, but >>>>>>>>> for >>>>>>>>> string >>>>>>>>> type, there doesn't seem to be one. >>>>>>>>> So if incoming Xml looks something like this: >>>>>>>>> <Person> >>>>>>>>> <firstname>Jiho</firstname> >>>>>>>>> </Person> >>>>>>>>> when deserialized into a Person object, lastname field will >>>>>>>>> contain >>>>>>>>> null, which doesn't tell me whether the field is simply >>>>>>>>> missing >>>>>>>>> (thus >>>>>>>>> safely ignored) or lastname field should be set to null (in >>>>>>>>> the >>>>>>>>> database, for example). >>>>>>>>> Any idea how to go about this? >>>>>>>>> Thanks in advance. >>>>>>>>> Jiho Han >>>>>>>>> Senior Software Engineer >>>>>>>>> Infinity Info Systems >>>>>>>>> The Sales Technology Experts >>>>>>>>> Tel: 212.563.4400 x216 >>>>>>>>> Fax: 212.760.0540 >>>>>>>>> jhan@infinityinfo.com >>>>>>>>> www.infinityinfo.com
[quoted text, click to view]
Jiho Han" <jihohan@yahoo.com> wrote in message news:a19ab9b61bc1b8c87f6f400e0b53@msnews.microsoft.com... > John, > > I don't know, you tell me, are these two different? > > <Person> > <FirstName xsi:nil = "true" /> > <Person> > > <Person> > </Person> > I don't know, either, which is why I asked the question. They certainly don't appear to be different in the intent of the document creator. John
[quoted text, click to view]
"Jiho Han" <jihohan@yahoo.com> wrote in message news:a19ab9b61bc328c87f701393053c@msnews.microsoft.com... > (Answering my own question) from the w3c rec, > > 2.6.2 xsi:nil > > XML Schema: Structures introduces a mechanism for signaling that an > element should be accepted as ·valid· when it has no content despite a > content type which does not require or even necessarily allow empty > content. An element may be ·valid· without content if it has the attribute > xsi:nil with the value true. An element so labeled must be empty, but can > carry attributes if permitted by the corresponding complex type. > > which tells me, "nillability" is strictly about the content of an element. > So in that case, a missing optional element vs. a nillable element which > possibly can carry attributes, are different. > > btw, in my schema, FirstName would be defined this ways: > > <xs:element name="FirstName" minOccurs="0" nillable="true"/> Ok, so is there a difference to you between a person with no first name, and a person with ... no first name? John
Actually, the intention is what you make of it in this case, because I am
the publisher of the schema. If I am accepting the document for an update method, for example, I could take the first form as saying set FirstName to null and the second form as saying, well, nothing. Don't do anything to FirstName at all. All this to say, the default xml deserialization does not distinguish between the first and the latter. I think, though, I can use a custom schema provider for this, then implement IXmlSerializable on the class so that I can examine the xsi:nil attribute upon deserializing. We'll see how that goes. [quoted text, click to view] > Jiho Han" <jihohan@yahoo.com> wrote in message > news:a19ab9b61bc1b8c87f6f400e0b53@msnews.microsoft.com... > >> John, >> >> I don't know, you tell me, are these two different? >> >> <Person> >> <FirstName xsi:nil = "true" /> >> <Person> >> <Person> >> </Person> > I don't know, either, which is why I asked the question. > > They certainly don't appear to be different in the intent of the > document creator. > > John >
You could also try changing the schema to include the two alternatives
clearly specified. You could, for instance, create a global "doNotTouch" attribute, and use it on the <FirstName> or wherever else. The sender could explicitly indicate what he wants to do, and this question of similarities would be moot. John [quoted text, click to view] "Jiho Han" <jihohan@yahoo.com> wrote in message news:a19ab9b61f0068c87fa3bde3f324@msnews.microsoft.com... > Actually, the intention is what you make of it in this case, because I am > the publisher of the schema. > > If I am accepting the document for an update method, for example, I could > take the first form as saying set FirstName to null and the second form as > saying, well, nothing. Don't do anything to FirstName at all. > > All this to say, the default xml deserialization does not distinguish > between the first and the latter. > I think, though, I can use a custom schema provider for this, then > implement IXmlSerializable on the class so that I can examine the xsi:nil > attribute upon deserializing. We'll see how that goes. > >> Jiho Han" <jihohan@yahoo.com> wrote in message >> news:a19ab9b61bc1b8c87f6f400e0b53@msnews.microsoft.com... >> >>> John, >>> >>> I don't know, you tell me, are these two different? >>> >>> <Person> >>> <FirstName xsi:nil = "true" /> >>> <Person> >>> <Person> >>> </Person> >> I don't know, either, which is why I asked the question. >> >> They certainly don't appear to be different in the intent of the >> document creator. >> >> John >> > >
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 |