Please refer to the following under the question:
Are there any documented web service bugs in Microsoft .NET Framework? 

http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/DotNetInterop

I think this might be relevent.
Rick Kellogg

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 12:47 PM
To: [EMAIL PROTECTED]
Subject: Re: null array element serialization




If the .net framework is representing a nil element as an empty string,
that sounds like a bug in the .net implementation.  Not much you can do
about it.  Who ever's implementing the .net client will have to develop a
work-around in their code.


Ian

Ian D. Stewart
Open Systems Engineer II
Enterprise Midrange - Bank One Infrastructure & Operations
[EMAIL PROTECTED]
(614) 213-6100




"Paolo Paganotto" <[EMAIL PROTECTED]> on 06/11/2003 11:14:59 AM

Please respond to [EMAIL PROTECTED]

To:   "AXIS" <[EMAIL PROTECTED]>
cc:

Subject:  null array element serialization



Hallo all,

I've to face this problem:
I've an array of strings that is part of a complex bean that is sent as
parameter of a web service from Java to .NET
If there is a null element in this array, this is parsed as follows in the
soap message: <item xsi:nil="true"/>
the problem is that .NET converts this element of my array as an empty
string "" rather than a null string, that is the behaviour I wish to
obtain.
How could I get a null element in my array at .NET site?

Could someone help me?

Thank you very much,


Paolo










This transmission may contain information that is privileged, confidential and/or 
exempt from disclosure under applicable law. If you are not the intended recipient, 
you are hereby notified that any disclosure, copying, distribution, or use of the 
information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. 
If you received this transmission in error, please immediately contact the sender and 
destroy the material in its entirety, whether in electronic or hard copy format. Thank 
you.



Reply via email to