Mailing-List: contact soap-dev-help@xml.apache.org; run by ezmlm
Message-ID: <05e101c17e28$987ee850$cea17cca@watson.ibm.com>
From: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
To: <soap-dev@xml.apache.org>
References: <3C0E4D10.43421DDA@genome.wi.mit.edu>
Subject: Re: NullPointerException when serializing null String objects
Date: Thu, 6 Dec 2001 13:35:32 +0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

How did you serialize the string? If its a parameter to an RPC
call the null value should be handled correctly. 

Can you post the code that shows the problem please?

Sanjiva.

----- Original Message ----- 
From: "David Turner" <turner@genome.wi.mit.edu>
To: <soap-dev@xml.apache.org>
Sent: Wednesday, December 05, 2001 10:36 PM
Subject: NullPointerException when serializing null String objects


> 
> I ran into a problem with SOAP's current String serialization when it
> encounters null String objects.   I couldn't find anything in either the
> user or dev archives regarding this so I don't know if this is a bug or
> not.
> 
> I ended up writing my own String serializer which handled the null
> situation.  I only used my String serializer on the client side when
> sending data to the service -- the soap service just uses the default
> soap String serializer/deseralizer.   I have attached the source code
> for my String serializer in case it can be incorporated into SOAP.
> 
> What I would like to know is if this is currently an issue or not?   Is
> SOAP currently able to handle null String objects during serializing?
> 
> Much appreciated.
> 
> David
> 
> 
> 
> 
> I
> 
> 
>