Hi Paul,
Thanks for the info. I have filtered out all the null cases so I don't see it
anymore.
-ted
On 12/5/11 2:46 AM, "paul nibin" <nibin....@gmail.com> wrote:
Hi,
I think this was an issue and it got fixed in the Axis 2 1.7.0. You could try
this test case in the latest nightly build.
Regards,
Paul
On Sun, Dec 4, 2011 at 3:33 AM, Ted Zeng <z...@adobe.com> wrote:
Hi all,
I pass some parameters as strings. Things work fine, except when a string is
"null".
Then the "null" would shift to the end. So I have a parameter list:
"1", "null", "3"
Then the server side would receive:
"1","3","null"
Why would this happen? Is there anything I could do to fix this other than
checking the parameters
Before sending out and modify the "null" to something else?
<xs:element name="insertDevice">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="args0" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args1" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args2" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args3" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args4" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args5" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args6" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args7" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args8" nillable="true"
type="xs:string"/>
<xs:element minOccurs="0" name="args9" nillable="true"
type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
Ted Zeng
AIR Android
Adobe Systems
