I'm having a problem with a Microsoft .NET service
(MapPoint) choking on any (I think it's any, but I'm
not positive) element that contains nil="true", as in
<Pushpins xsi:nil="true"/>
<Route xsi:nil="true"/>
Axis 1.0 eliminated these elements from the request,
which makes the .NET service happy, but 1.1 includes
them.
The year-old, archive message (below) seems to be
related, but the wsdl looks like it already has
minOccurs="0" maxOccurs="1" as in this snippet:
<s:complexType name="MapSpecification">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1"
name="Pushpins" type="s0:ArrayOfPushpin"/>
<s:element minOccurs="0" maxOccurs="1"
name="Route" type="s0:Route"/>
</s:sequence>
</s:complexType>
Any suggestions about how to fix, or work around this
problem.
>From the archives:
Subject: RE: nil = "true"
From: Tom Jordahl <tomj () macromedia ! com>
Date: 2002-07-31 13:58:51
If you are using a document/literal service, you can
change the WSDL to have \
minoccurs=0 maxoccurs=1. Then if the value if null,
it will be omitted from the XML \
in the request/response.
If you are using rpc/encoded, you can't do this as
encoded will always use nil=true.
See the test in java/test/wsdl/omit for an example.
--
Tom Jordahl
Macromedia
-----Original Message-----
From: Snigdha Pandit [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 31, 2002 5:57 AM
To: Axis Users
Subject: xsi:nil = "true"
hi All,
How can I eliminate elements with xsi:nil attribute
set to true?
Thanks and Regards
Snigdha
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
