I'm accessing a sample weather web service at <a href="http://live.capescience.com/wsdl/GlobalWeather.wsdl" target="_blank">http://live.capescience.com/wsdl/GlobalWeather.wsdl</a> via SOAP_WSDL. There are two bindings within that service (if this is the correct terminology): "StationInfo" and "GlobalWeather". After creating creating the proxy object, I only have access to the StationInfo methods. The StationInfo binding is defined first in the WSDL, so I don't think this is a coincidence. In other words, the following code:<br /><br /><!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->require_once 'SOAP/Client.php';<br />$wsdl = new SOAP_WSDL('http://live.capescience.com/wsdl/GlobalWeather.wsdl');<br />$weather = $wsdl->getProxy();<!--c2--></div><!--ec2--><br /><br />yields an object ($weather) with only the StationInfo methods. I tried:<br /><br /><!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->$weather = $wsdl->getProxy('GlobalWeather');<!--c2--></div><!--ec2--><br /><br />but that fails deep within the bowels of SOAP_WSDL.<br /><br /> Does anyone know how to access the "other" binding? I must be missing something.<br /><br />Thanks for any help. A reference to an online resource with plenty of examples that explain the above would be greatly appreciated.<br /><br />Dorsey<!--content-->
Either no one knows the answer or no one else is interested, but I've found the solution. Invoking the setPort( string ) method will access any port defined by the WSDL.<!--content-->
thanks for the update, even though its over my head<br />it may help someone.<!--content-->
Thanks for the update, Dorsey.<br /><br />I'm sorry we missed your post the first time but I'm glad to see you found your way. Thumbs Up<!--content-->
Either no one knows the answer or no one else is interested, but I've found the solution. Invoking the setPort( string ) method will access any port defined by the WSDL.<!--content-->
thanks for the update, even though its over my head<br />it may help someone.<!--content-->
Thanks for the update, Dorsey.<br /><br />I'm sorry we missed your post the first time but I'm glad to see you found your way. Thumbs Up<!--content-->