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

[James Clark]

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

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.

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)?

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

> 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 

Agreed.

James