Yes it behaves in the same manner. Thanks, Keith.
On Fri, Apr 24, 2009 at 9:27 PM, McCullough, Ryan <rmccullo...@rightnow.com>wrote: > If you have an element on a complexType that has nillable=”true” and > minOccurs=”0”, will the element be de-serialized if the property on the soap > stub is set to null? > > > > For instance, let’s say a portion of your XSD looks like this: > > <xs:complexType name="point" > > > <xs:sequence> > > <xs:element name="x" type="xs:int" nillable="true" minOccurs="0" > maxOccurs="1" /> > > <xs:element name="y" type="xs:int" nillable="true" minOccurs="0" > maxOccurs="1" /> > > </xs:sequence> > > </xs:complexType> > > > > If in your generated soap stub object you set x = null and y = 20, will the > de-serialized xml look like this: > > <point> > > <x xsi:nil="true" /> > > <y>20</y> > > </point> > > > > I know that Axis 1.4 (not Axis2) will not de-serialize the element when it > is set to null and has minOccurs=”0”. If need be I can dig up the specific > code where this happens. > > > > The question I have is if Axis2 also behaves this way? > > * * > > *Ryan McCullough* | *RightNow Technologies* | Integration Tools Engineer > > 406-556-3162 office | Bozeman, MT | rmccullo...@rightnow.com | > http://www.rightnow.com > > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
