Hello all,
I believe Dave already forwarded the code to this list. Please
take a look at this thread to find it.
Best,
-B
-----------------------
Brian Gilman <[EMAIL PROTECTED]>
Sr. Software Engineer MIT/Whitehead Inst. Center for Genome Research
One Kendall Square, Bldg. 300 / Cambridge, MA 02139-1561 USA
phone +1 617 252 1069 / fax +1 617 252 1902
On Thu, 6 Dec 2001, Sanjiva Weerawarana wrote:
> 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" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> 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
> >
> >
> >
>
>
