Posted by Steve on 01/12/07 00:48

"Hendri Kurniawan" <ask-me@email.com> wrote in message
news:12qdcu63ij1tgcc@corp.supernews.com...
| Steve wrote:
| > "Gerry Vandermaesen" <gerry.vandermaesen@gmail.com> wrote in message
| > news:1168509369.708206.125320@i56g2000hsf.googlegroups.com...
| > | Hi,
| > |
| > | I am currently having the exact same problem as described here:
| > |
| > | http://bugs.php.net/bug.php?id=36226
| > |
| > | The webservice is configured to return 0-* objects of a complextype,
| > | but when only one single item is returned, it does not get
deserialized
| > | as an array as I would expect, but as a single object.
| > |
| > | The new feature proposed on the bottom of the above page does not seem
| > | to be included in our installed version of PHP 5.1.2-1.
| > |
| > | Is there any other way to change this behaviour.
| > |
| > | Kind regards.
| >
| > $complexType = yourCallToWebService;
| > if (!is_array($complexType)){ $complexType = array($complexType); }
| >
| > perhaps? haven't played with that too much.
| >
| >
|
| Because it is an array of arrays, simply checking is_array will always
| return true.

interesting. i had thought that if $complexType was nothing (an unitialized
array for instance), that declaring an array initialized with nothing
(uninitialized array - $complexType) would make the array be likewise
uninitialized. i'll have to check that...just hadn't run across that before.
thanks for the heads-up.

[Back to original message]