As per the SOAP 1.1 specification, the construct "xsi:null=1" seems to be the right way to represent NULL values.
(Note that this contrasts with the XML Schema mechanism of using "xsi:nil=true" !!) So .. is this a bug in Apache SOAP ? I'd appreciate any suggestions/ideas ... thanx -john ----- Original Message ----- From: "Karappan, Raju M" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 05, 2002 12:41 PM Subject: RE: null handling in apache soap2.2 > > Aache SOAP is expecting xsi:null='true' instead of xsi:null='1' > in <return xsi:null='true' xsi:type='bean.Person'></return>. > And I think (not sure) according to the w3 specs that is true. > > Raju > > > > > <SOAP-env: > ...... > <getPersonResponse> > <return xsi:null='1' xsi:type='bean.Person'></return> > </getPersonResponse> > <SOAP-env> > > > > -----Original Message----- > > From: John Mani [SMTP:[EMAIL PROTECTED]] > > Sent: Friday, April 05, 2002 12:48 PM > > To: [EMAIL PROTECTED] > > Subject: Re: null handling in apache soap2.2 > > > > > This looks like a null object to me, with xsi:null='1': > > > <return xsi:null='1' xsi:type='bean.Person'></return> > > > > > > Wouldn't an empty Person object look like > > > <return xsi:type='bean.Person'><fieldname > > xsi:type='fieldType'/></return> > > > > Yup, that's what I thought too .. a bug in Apache SOAP ? Or are we > > missing something ? > > > > (btw, Sun's JAX-RPC implemetation also exhibits similar behaviour) > > > > -john > > > > > > > > > > > > > > "John Mani" > > > <john@sixthdimens To: > > <[EMAIL PROTECTED]> > > > ion.com> cc: > > > Subject: null handling > > in > > apache soap2.2 > > > 05/04/2002 08:26 > > > Please respond to > > > soap-user > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > I'm implementing an apache SOAP client that interacts with a WebLogic > > 6.1 > > > sp2 > > > based SOAP server application. > > > > > > The server has a method that's supposed to return a null object. > > > For example, > > > Person getPerson(String id) > > > and if this 'id' is bogus, this method returns a null object. Note that > > the > > > Person > > > class is a standard JavaBean. > > > > > > Now, when I actually invoke this method on the weblogic hosted service > > with > > > a bogus id, I get the following XML fragment as the SOAP response: > > > > > > <SOAP-env: > > > ...... > > > <getPersonResponse> > > > <return xsi:null='1' xsi:type='bean.Person'></return> > > > </getPersonResponse> > > > <SOAP-env> > > > > > > I was assuming that the SOAP deserializer would convert this into a > > 'null' > > > object. > > > Instead, within my apache based client, I get a Person object that has > > null > > > fields within. > > > > > > btw, I'm using Apache SOAP 2.2 on the client side, with the standard > > > BeanSerializer/BeanDeserializer used to marshall/unmarshall the .java > > > classes > > > > > > thanx > > > -john > > > > > > > > > > > > > > > > > > > > > > > > > > > >
