On Thu, 27 Jun 2002, Sam Ruby wrote: > > I think you can drop the 'nil' change for now - it only help > > Axis to accept the input from ApacheSoap, but not the reverse - > > Axis will still send nil which apacheSoap will not recognize. > > What version of Apache SOAP are you using? From what I can see, this > was fixed on June 10th, and then released the same day. See > >http://cvs.apache.org/viewcvs.cgi/xml-soap/java/src/org/apache/soap/encoding/soapenc/SoapEncUtils.java > > and http://xml.apache.org/soap/releases.html#v2.3.1
I used an older version initially, but now I updated to HEAD. Now apacheSOAP sends nil, but of course that doesn't change the fact that Axis doesn't accept 'null' - which I think it should. > > I have no idea how to fix this one - I think I'll just give > > up on making apache soap talk with axis, there are too many > > problems. > > Regarding interoperability, I only recall you bringing up this one > issue. Are there others? I sent another mail - it's about axis not sending the type for null objects. I initially tought it's the nil/null problem, but with some debug it seems ApacheSOAP does recognize the null corectly, but can't determine the type. Costin
