ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Fell <s...@zaks.demon.co.uk>
Subject [PATCH] Re: xsi:null handling
Date Sun, 09 Jun 2002 18:55:22 GMT
I've attached a patch for this. I've also attached a patch for the
interop sample deployment descriptor, which was using empty namespaces
with a prefix [ xmlns:x="" ] which isn't valid, and Xerces (2.0.1) was
throwing an error.


Cheers
Simon
www.pocketsoap.com

On Sun, 9 Jun 2002 01:13:53 +0600, in soap you wrote:

>Hi Simon,
>
>Was this in the 2.3 codebase? If so I agree this'll be a big
>problem and probably sufficient cause for a 2.3.1 to be 
>released ASAP.
>
>I agree it needs to be fixed right to work with both XSD
>versions.
>
>Thanks!
>
>Sanjiva.
>
>----- Original Message ----- 
>From: "Simon Fell" <soap@zaks.demon.co.uk>
>To: <soap-dev@xml.apache.org>
>Sent: Saturday, June 08, 2002 8:45 AM
>Subject: xsi:null handling
>
>
>> I noticed that Apache SOAP always serializes NULLs with
>> xsi:null="true", the problem is that for the 2001 schema version there
>> is no null attribute it got renamed to nil.
>> 
>> The quick fix is to change the definition of ATTR_NULL in
>> constants.java, however it looks like the code supports both 1999 and
>> 2001 schema, so really it needs to pick the correct attribute name
>> based on the schema version in use.
>> 
>> This will be a significant interop issue for people using nulls
>> between Apache and non-Apache toolkits.
>> 
>> Cheers
>> Simon
>> www.pocketsoap.com


Mime
View raw message