<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 08 Aug 2008 16:24:03 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Eirik Hoem's Blog: Array problems with SOAP and PHP - Updated]]></title>
      <guid>http://www.phpdeveloper.org/news/9790</guid>
      <link>http://www.phpdeveloper.org/news/9790</link>
      <description><![CDATA[<p>
<i>Eirik Hoem</i> has <a href="http://eirikhoem.wordpress.com/2008/03/13/array-problems-with-soap-and-php-updated/">posted an update</a> on a <a href="http://eirikhoem.wordpress.com/2007/05/23/array-problems-with-x-fire-soap-and-php">previous problem</a> he was having when working with SOAP in PHP and its handling of arrays.
</p>
<blockquote>
The scenario was that when an array with only one object was returned over SOAP the array was discarded and pointed straight to the single object.
</blockquote>
<p>
Come to find out, this behavior wasn't a bug, it was <a href="http://bugs.php.net/bug.php?id=36226">a feature</a> - the fix is to add another parameter to the initialization of the SoapClient to add the SOAP_SINGLE_ELEMENT_ARRAYS feature.
</p>]]></description>
      <pubDate>Thu, 13 Mar 2008 10:22:19 -0500</pubDate>
    </item>
  </channel>
</rss>
