[Fwd: Re: [wsf-c-dev] Dynamic Client API [ PHP ]]

[Sanjiva Weerawarana]

Sorry this should've been on the list!

-------- Original Message --------
Subject: Re: [wsf-c-dev] Dynamic Client API [ PHP ]
Date: Thu, 21 Dec 2006 22:44:33 +0530
From: Sanjiva Weerawarana <sanjiva at wso2.com>
Organization: WSO2 Inc.
To: James Clark <james at wso2.com>
References: <45878150.3050508 at wso2.com>	 
<1166509344.5197.57.camel at tamarind.home.jclark.com>	 
<1166517976.5197.117.camel at tamarind.home.jclark.com>	 
<45889010.9080307 at wso2.com> 
<1166670965.5197.229.camel at tamarind.home.jclark.com>

James Clark wrote:
>> The right thing to do is to have an option called "port" for wsdl 1.1 and 
>> "endpoint" for wsdl 2.0.
> 
> If the only WSDL 2.0 option is "endpoint", then the value would I guess
> need to be of the form "foo/bar" where foo is the local name of the
> service and bar is the local name of the endpoint within the service.

Yeah sorry I made a mistake .. it needs to be two bits of info: service
name and port/endpoint name.

> Wouldn't it be simpler to have to separate service and endpoint options,
> each taking a local name, so that in the case where there's a single
> service, the user can specify just the endpoint name and in the case
> where there's multiple services each with a single endpoint, the user
> can specify just the service name?

+1.

> Also is it really a good idea to make the user modify their PHP code if
> they upgrade from WSDL 1.1 to WSDL 2.0?  I would suggest allowing the
> user to use either the option name "port" or "endpoint" regardless of
> whether they use WSDL 1.1 or WSDL 2.0.

+1 for using endpoint; we've adopted wsdl 2.0 terminology wherever possible.

> This brings me to another question: how do they know whether they will
> get WSDL 1.1 or WSDL 2.0 when they do a use a http://...?wsdl URI (and
> how in the future will be know whether to generate WSDL 1.1 or 2.0)?

Our plan is to use ?wsdl and ?wsdl2. Also, wsdl 2.0 has a defined media
type whereas wsdl 1.1 goes as text/xml. Worst case you have to sniff the data.

>> If the user does not indicate a port to use, then we should
>> automatically pick up the first soap port as the default.
> 
> I don't have a better solution, but the thing that bothers me about that
> is that in the component model for WSDL 2.0, the value of both the
> services property of a description and the endpoints property of a
> service is an *unordered* set. In other words, we are making order
> significant when the spec is explicitly saying that is not significant.

True .. the only other option is to fault in this case saying "you gotta
help me out". I can live with that too.

Sanjiva.
-- 
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."


-- 
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."