tag:help-archives.hannonhill.com,2010-02-09:/discussions/web-services/24-no-subjectCascade CMS: Discussion 2013-12-12T20:06:23Ztag:help-archives.hannonhill.com,2010-02-09:Comment/32843092010-10-12T02:47:28Z2010-10-12T02:47:28ZWeb Services Error: No schema asset was bundled with the Edit request<div><p>Try removing the <code>entityType</code> field of the <code>page</code>:<br />
</p>
<pre><code>[entityType] => stdClass Object
(
[name] => page
)</code></pre>
<p>We're working on a fix for that issue in a future version.</p></div>Rosstag:help-archives.hannonhill.com,2010-02-09:Comment/32843092010-10-12T14:29:27Z2010-10-12T14:29:27ZWeb Services Error: No schema asset was bundled with the Edit request<div><p>I tried removing the entityType completely and removing just the name variable of the entityType, but I still get the error about not having a schema asset.</p></div>Bryan Zeratag:help-archives.hannonhill.com,2010-02-09:Comment/32843092010-10-13T17:06:16Z2010-10-13T17:06:16ZWeb Services Error: No schema asset was bundled with the Edit request<div><p>Would it be possible to send the actual SOAP XML that's being sent on the wire instead of the PHP object dump? You can obtain that in PHP by calling the SOAP client's <code>__getLastRequest()</code> method.</p></div>Rosstag:help-archives.hannonhill.com,2010-02-09:Comment/32843092010-10-13T18:59:59Z2010-10-13T19:10:26ZWeb Services Error: No schema asset was bundled with the Edit request<div><p>Now I see where the problem lies. Here's the XML:<br />
` <SOAP-ENV:Envelope xmlns:SOAP-ENV="<a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>" xmlns:ns1="<a href="http://www.hannonhill.com/ws/ns/AssetOperationService">http://www.hannonhill.com/ws/ns/AssetOperationService</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>"></p>
<pre><code><SOAP-ENV:Body>
<ns1:edit>
<ns1:authentication>
<ns1:password>*****</ns1:password>
<ns1:username>bzera</ns1:username>
</ns1:authentication>
<ns1:asset>
<ns1:feedBlock xsi:nil="true"/>
</ns1:asset>
</ns1:edit>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>`</code></pre>
<p>The actual asset isn't being encoded to XML and passed. I know this is no longer an issue with your software, but do you have any idea why the SoapClient class would not be able to construct an asset's XML? If not, that's fine. Thanks.</p></div>Bryan Zeratag:help-archives.hannonhill.com,2010-02-09:Comment/32843092010-10-14T02:18:47Z2010-10-14T02:19:38ZWeb Services Error: No schema asset was bundled with the Edit request<div><p>Brian,</p>
<p>Try using the <code>SOAP_SINGLE_ELEMENT_ARRAYS</code> option of the SoapClient<br />
constructor. This affects the way that SoapClient converts SOAP XML to/from<br />
PHP objects when it encounters something in the WSDL that <em>might</em> appear<br />
more than one time but doesn't. I recall that not specifying<br />
<code>SOAP_SINGLE_ELEMENT_ARRAYS</code> can cause some weirdness in how PHP handles
complex WSDL like Cascade's. I'm looking at your <code>var_dump()</code> of the array,<br />
though, and it's not clicking with me why only <code>feedBlock</code> is being<br />
serialized to XML. Usually I see that problem when I've accidentally tried<br />
to define more than one <code>asset</code>, for example:<br />
</p>
<pre><code>$request['asset'] = array('page'=>$something);
$request['asset'] = array('feedBlock'=>$somethingElse);</code></pre>
<p>But that doesn't appear to be what's going on in your case. Just including<br />
the example for discussion's sake. There is a reasonable discussion of<br />
<code>SOAP_SINGLE_ELEMENT_ARRAYS</code> on <a href="http://www.dotvoid.com/2008/10/soap-structures-in-php/">this blog</a>.</p>
<p>I'm resolving the issue here because I don't think there's any more<br />
Cascade-related help we can provide, but feel free to reopen it if you run<br />
into anything.</p>
<p>Ross</p>
<p>On Wed, Oct 13, 2010 at 3:02 PM, bzera <<br />
<a href="mailto:tender+d1256ca5b64dd78ae2440d23c299e60438cfc37ef@tenderapp.com">tender+d1256ca5b64dd78ae2440d23c299e60438cfc37ef@tenderapp.com</a><<a href="mailto:tender%2Bd1256ca5b64dd78ae2440d23c299e60438cfc37ef@tenderapp.com">tender%2Bd1256ca5b64dd78ae2440d23c299e60438cfc37ef@tenderapp.com</a>><br />
</p>
<blockquote><p>wrote:</p></blockquote></div>Ross