----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 27, 2002 2:51 PM Subject: Re: HashMap/Hashtable, nil/null and timing.
> On Thu, 27 Jun 2002, Scott Nichol wrote: > > > > > First, I noticed that apache-soap is sometimes using 'null' while > > > > axis is using 'nil'. I have no idea why this happens - but it > > > > affects the interoperability ( i.e. can't make calls from apache-soap > > > > to axis ). I have a simple patch that would accept null - let me know > > > > if I can send it. > > > > Are you seeing this using Apache SOAP 2.3.1? I believe Matt added code for > > that release specifically related to emitting nil v. null depending on the > > XSI namespace (I think older schemas like 1999 used null instead of nil). > > If there is still a problem with 2.3.1, could you please submit a bugzilla > > report for SOAP (not Axis)? > > I can't modify the ApacheSOAP version. > > I'm not sure I understand - is 'null' valid in the 99 schema ? Isn't Axis > supposed to interoperate with that particular schema ? I find it hard to > believe that this level of backward incompatibility is possible. In the 1999 and 2000 schemas, 'null' is the name of the attribute. In the 2001 schema, 'nil' is the name. Prior to version 2.3.1, Apache SOAP has a bug in which it uses 'null' with the 2001 schema. Starting with 2.3.1, the bug is fixed. Therefore, if you have an older version and are using the 2001 schema, it is this bug that could prevent you from interoperating. If you are using the 1999 or 2000 schema, Apache SOAP correctly emits the name as 'null' and I believe that any interop problems would be the fault of Axis. Scott Nichol
