[wsf-c-dev] Dynamic Client API [ PHP ]

Sanjiva Weerawarana sanjiva at wso2.com
Tue Dec 19 17:21:20 PST 2006


The right thing to do is to have an option called "port" for wsdl 1.1 and 
"endpoint" for wsdl 2.0.

Its not about the interface- its about the soap or http binding that the 
user wants to use. The binding indicates the interface. If the user does 
not indicate a port to use, then we should automatically pick up the first 
soap port as the default.

There's no way ext/soap code does wsdl 2.0 and I doubt it ever will. I 
think we need to do that on our own later; there's no big rush for it yet 
but it would be great to have it soon because we can take serious 
ownership of wsdl 2.0 support then.

Sanjiva.

James Clark wrote:
>>> WSClient::getProxy(string interface)
>>>
>>> returns the WSClientProxy object for the specified interface.
>> Make the interface argument optional.  If getProxy doesn't specify the
>> interface, and the WSClient options do, then use that to determine the
>> proxy, otherwise do the same as the WSClientProxy constructor with no
>> interface specified.
> 
> A better solution is for getProxy to take an optional options array; as
> well as "interface", you would be able to specify any of the
> message-level properties.
> 
> James
> 
> 
> 
> _______________________________________________
> Wsf-c-dev mailing list
> Wsf-c-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev
> 

-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: sanjiva at wso2.com; cell: +94 77 787 6880; fax: +1 509 691 2000

"Oxygenating the Web Service Platform."





More information about the Wsf-c-dev mailing list