You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Dave Reid <da...@wmode.com> on 2002/04/19 00:54:40 UTC

RE: boolean value interpretation by Apache SOAP

We have come across a related problem - parsing of the "null" tag has the
same interpretation problem with recognizing "true" but not "1". The null
tag is used when passing parameters that have a null value - .NET passes
xsi:null="1", which is interpreted by Apache SOAP as NOT null.

This is still a problem in the latest version of SoapEncUtils.isNull(). To
me it looks like a good solution is to move the "isBooleanTrueValue(String
v)" functionality from BooleanDeserializer into a static method of that
class, and call that method from SoapEncUtils.isNull(). Or perhaps the new
method would be more natural in SoapEncUtils?

What is the best way to get this fixed?

..Dave Reid

-----Original Message-----
From: Sam Ruby [mailto:rubys@us.ibm.com]
Sent: Thursday, August 02, 2001 4:23 AM
To: soap-user@xml.apache.org
Subject: Re: boolean value interpretation by Apache SOAP


Fixed in the latest CVS.  You can find prebuilt binaries at
http://xml.apache.org/dist/soap/nightly/.

- Sam Ruby

RE: boolean value interpretation by Apache SOAP

Posted by Dave Reid <da...@wmode.com>.
Gary, check out http://www.perfectxml.com/articles/xml/soapguide.asp. That
shows how to solve your specifc "result" problem (short answer - you have to
code the client to "know" what to expect). The equivalent in a deployment
descriptor, for use at the server is:
    <!-- "parameter name" aliases
         We need "parameter name" aliases for some types because .NET does
not
	 pass the type when it passes a null object; all we get is the parameter
       name (in an unqualified namespace). These mappings do NOT specify a
	 javaType or java2XMLClassName, so that they are never used for outgoing
	 serialization. -->
    <isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
             qname=":someStringParametersName"

xml2JavaClassName="org.apache.soap.encoding.soapenc.StringDeserializer"/>

..Dave Reid

-----Original Message-----
From: Gary K. Nitzberg [mailto:gknitz@nitzspace.com]
Sent: Thursday, April 18, 2002 5:15 PM
To: soap-user@xml.apache.org
Subject: RE: boolean value interpretation by Apache SOAP



OK, this is part of my deserializer 'no value' problem yesterday.  How do
you deserialize?   <result xsi:null="1"/>

Is it an integer, string or boolean???





At 04:54 PM 4/18/02 -0600, you wrote:
>We have come across a related problem - parsing of the "null" tag has the
>same interpretation problem with recognizing "true" but not "1". The null
>tag is used when passing parameters that have a null value - .NET passes
>xsi:null="1", which is interpreted by Apache SOAP as NOT null.
>
>This is still a problem in the latest version of SoapEncUtils.isNull(). To
>me it looks like a good solution is to move the "isBooleanTrueValue(String
>v)" functionality from BooleanDeserializer into a static method of that
>class, and call that method from SoapEncUtils.isNull(). Or perhaps the new
>method would be more natural in SoapEncUtils?
>
>What is the best way to get this fixed?
>
>..Dave Reid
>
>-----Original Message-----
>From: Sam Ruby [mailto:rubys@us.ibm.com]
>Sent: Thursday, August 02, 2001 4:23 AM
>To: soap-user@xml.apache.org
>Subject: Re: boolean value interpretation by Apache SOAP
>
>
>Fixed in the latest CVS.  You can find prebuilt binaries at
>http://xml.apache.org/dist/soap/nightly/.
>
>- Sam Ruby

RE: boolean value interpretation by Apache SOAP

Posted by "Gary K. Nitzberg" <gk...@nitzspace.com>.
OK, this is part of my deserializer 'no value' problem yesterday.  How do 
you deserialize?   <result xsi:null="1"/>

Is it an integer, string or boolean???





At 04:54 PM 4/18/02 -0600, you wrote:
>We have come across a related problem - parsing of the "null" tag has the
>same interpretation problem with recognizing "true" but not "1". The null
>tag is used when passing parameters that have a null value - .NET passes
>xsi:null="1", which is interpreted by Apache SOAP as NOT null.
>
>This is still a problem in the latest version of SoapEncUtils.isNull(). To
>me it looks like a good solution is to move the "isBooleanTrueValue(String
>v)" functionality from BooleanDeserializer into a static method of that
>class, and call that method from SoapEncUtils.isNull(). Or perhaps the new
>method would be more natural in SoapEncUtils?
>
>What is the best way to get this fixed?
>
>..Dave Reid
>
>-----Original Message-----
>From: Sam Ruby [mailto:rubys@us.ibm.com]
>Sent: Thursday, August 02, 2001 4:23 AM
>To: soap-user@xml.apache.org
>Subject: Re: boolean value interpretation by Apache SOAP
>
>
>Fixed in the latest CVS.  You can find prebuilt binaries at
>http://xml.apache.org/dist/soap/nightly/.
>
>- Sam Ruby