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. Probably I have to use ApacheSOAP on both ends - it seems the peformance differences are pretty small ( in some cases I get slightly worse numbers ), and combined with the Hashtable/HashMap issue it makes it too painfull to switch to axis. Costin
