983Re: MSTK2 and null
- Apr 1, 2001Indeed, null != empty string.
However, the declaration SOAP-ENC:arrayType="xsd:string" does not
preclude that some elements of the array might be null
(whatever "null" means). The declaration merely says that whatever
element are present will be of type xsd:string or subtypes of
xsd:string and that there will not be more than four of them (in one
--- In soapbuilders@y..., "Fredrik Lundh" <fredrik@p...> wrote:
> manish wrote:
> > <inputStringArray SOAP-ENC:arrayType="xsd:string">
> > <item xsi:type="xsd:string">one</item>
> > <item xsi:type="xsd:string">two</item>
> > <item xsi:null="1" />
> > <item xsi:type="xsd:string">three</item>
> > </inputStringArray>
> > </m:echoStringArray>
> > </SOAP-ENV:Body>
> > </SOAP-ENV:Envelope>
> > The item 3 in the array is null, with attribute xsi:null="1"
> but in the array declaration, you telling the receiver
> that you're sending four strings.
> (null != empty string)
> Cheers /F
- << Previous post in topic Next post in topic >>