I ran into a problem using Apache SOAP 2.2 within WSAD (WebSphere Studio Application Developer IDE). To solve it the Apache SOAP jar had to appear before WSAD's webcontainer.jar in the CLASSPATH. There was a method conflict that caused the null objects to deserialize to objects built with the default constructor. You may have a similar conflict in one of your jar files.
Shawn. [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: 03/13/2002 10:53 Subject: Re: HELP : xsi:null="true" AM Please respond to soap-user On Wednesday 13 March 2002 12:05, you wrote: > Its xsi:nil and not xsi:null for specifying that an element value holds a > null value... dovle pretty sad to disappoint you but this is the answer that I am reveiving from my apache soap when an attribute has null value: (snapshot from UtilSnoop) <return xmlns:ns2="kns" xsi:type="ns2:test.TestSerializable"> <testVector xmlns:ns3="http://xml.apache.org/xml-soap" xsi:type="ns3:Vector" xsi:null="true"/> <name xsi:type="xsd:string" xsi:null="true"/> <number xsi:type="xsd:int">0</number> <valid xmlns:ns4="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:Array" ns4:arrayType="xsd:boolean[]" xsi:null="true"/> Are you shure that you receive the xsi:nil="true" ? I have read the Soap specification and I have found the same : A NULL value or a default value MAY be represented by omission of the accessor element. A NULL value MAY also be indicated by an accessor element containing the attribute xsi:null with value '1' or possibly other application-dependent attributes and values. (Quoting from W3C specs for ksoap1.1) So what could be wrong inhere ? Has anyone managed to send an struct object with null attribute values ? (I believe you have but ...) TIA for your answers dovle This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates.