Re: [SOAP] nested object in SOAP result

On 8 September 2010 15:43, nik600 <nik600@gmail.com> wrote: > On Wed, Sep 8, 2010 at 2:50 PM, Richard Quadling <rquadling@gmail.com> wrote: >> On 8 September 2010 11:25, nik600 <nik600@gmail.com> wrote: >>> On Wed, Sep 8, 2010 at 12:10 PM, Richard Quadling <rquadling@gmail.com> wrote: >>>> On 7 September 2010 19:12, nik600 <nik600@gmail.com> wrote: >>>>> >>> >> >> Scalar or Struct - that's the choice. An "array" is a struct. >> >> You are supplying an array of attributes. >> >> The struct is the array. >> >> Nothing is actually wrong. >> >> >> -- >> Richard Quadling >> Twitter : EE : Zend >> @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY >> > > Ok, but on server-side i can do > > foreach($Element->Elements as $v){ > // process Element $v > } > > and on client-side i have to do > > foreach($Element->Elements->Struct as $v){ > // process Element $v > } > > > -- > /*************/ > nik600 > http://www.kumbe.it > Yep! That's what your WSDL says it is. ElementA contains PropertyA1 and Elements (of type ElementB) ElementB is an array of PropertyB1s ElementA->Elements->ElementB->PropertyB1 The array is a construct in its own right. http://search.cpan.org/~rybskej/SOAP-Data-ComplexType-0.044/lib/SOAP/Data/ComplexType.pm#Using_arrays_and_Array_type_fields gives some more info on this. The "array" isn't part of this WSDL file, so it is just a structure and no dereferencing ( Elements->ElementB->PropertyB1 => Elements->PropertyB1) (Don't know the exact terminology). -- Richard Quadling Twitter : EE : Zend @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY