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)?
+1. Lets start with the wire dump, and determine the correct fix. For reference, http://www.w3.org/TR/xmlschema-0/#Nils http://www.w3.org/TR/2000/CR-xmlschema-0-20001024/#Nulls The original Apache SOAP didn't support 2001 schema because, well, it wasn't invented yet. ;-) The first attempts to support 2001 schema were incomplete. Let's figure out where this bug exists, how pervasive the problem is (was it merely a recent regression that has or has not already been fixed, etc), and determine the correct course of action from there. [EMAIL PROTECTED] wrote: > Hello ? Hello! > Anyone interested in interoperability or migration from ApacheSOAP ? With a passion! >>Second problem: it seems apache-soap uses Hashtable while Axis >>is using HashMap ( for soap map ). That creates pretty serious >>problems in migrating from a-soap to axis, as all the code will >>have to be changed. There are 3 (possible) solutions I found: >> >>- change the bean introspector to see if the attribute is Hashtable >>I couldn't understand the code, so I can't do that. One place to start is with the http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-axis/java/src/org/apache/axis/utils/JavaUtils.java class and take a look at the isConvertable and Convert methods. = = = I'm not sure everybody realizes this (perhaps not even Costin), but Costin is a committer to xml-soap. - Sam Ruby
