On Wed, Feb 15, 2012 at 4:58 PM, Greg Dritschler
<greg.dritsch...@gmail.com> wrote:
> When a web service binding uses wsdl.service, WebServiceBindingProcessor
> picks the first port.
>
> if (model.getPortName() != null) {
> port =
> service.getElement().getPort(model.getPortName());
> } else {
> // BWS20006 - no port specified so pick the first
> one
> port =
> (Port)service.getElement().getPorts().values().iterator().next();
> }
>
> What if the reference requires SOAP.v1_1 or SOAP.v1_2? Shouldn't it pick a
> port that uses a matching SOAP binding? The web services binding
> specification says:
>
> 139 If the binding is for an SCA reference, the set of available ports for
> the reference consists of the
> 140 ports in the WSDL service that have portTypes which are compatible
> supersets of the SCA
> 141 reference as defined in the SCA Assembly Model specification
> [SCA-Assembly] and satisfy all
> 142 the policy constraints of the binding.
Greg
Sounds right to me.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
