Anyone interested in updating/patching this library, let me know so I can send you diffs!
Looka wrote:
Using WSDL on .NET (new SharePoint) server doesn't return me ALL available parameters for available methods! It kinda hangs after parameter type that is complex. Like this:
My WSDL server returns this part:
<s:element name="GetListItems">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="listName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="viewName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="query">
<s:complexType mixed="true">
<s:sequence>
<s:any />
</s:sequence>
</s:complexType>
</s:element>
<s:element minOccurs="0" maxOccurs="1" name="viewFields">
<s:complexType mixed="true">
<s:sequence>
<s:any />
</s:sequence>
</s:complexType>
</s:element>
<s:element minOccurs="0" maxOccurs="1" name="rowLimit" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="queryOptions">
<s:complexType mixed="true">
<s:sequence>
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
And our SOAP client parses it like this:
[name] => GetListItems [namespace] => s0 [complex] => 1 [elements] => Array ( [listName] => Array ( [minOccurs] => 0 [maxOccurs] => 1 [name] => listName [type] => string [namespace] => s )
[viewName] => Array ( [minOccurs] => 0 [maxOccurs] => 1 [name] => viewName [type] => string [namespace] => s )
[query] => Array ( [minOccurs] => 0 [maxOccurs] => 1 [name] => query [namespace] => s0 )
)
It 'hangs' after first complex (non-string) type, and happens on all methods! So i get only 3 available params instead of 6!!! I think it's bug in wsdl.php somewhere, and I'll look it up, but maybe someone knows what the problem is?? Thanks!
Luka Jandric
-- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php