BINDINGS-23: Proposed resolution v5

[Simon Nash <oasis@cjnash.com>]

Based on the discussion on today's call, here is a revised set
of proposed spec changes to resolve BINDINGS-23:

1) In the first bullet (Service) under the /binding.ws/@wsdlElement
description, replace all the current text by the following:

   If the binding is for an SCA service, the wsdlElement attribute
   MUST NOT specify the wsdl.service form of URI.

   If the binding is for an SCA reference, the set of available ports
   for the reference consists of the ports in the WSDL Service that
   . have portTypes which are compatible supersets of the SCA reference
     as defined in the SCA Assembly Model specification [SCA-Assembly], and
   . are able to satisfy all the policy constraints of the SCA reference.

   The set of available ports for the reference MUST contain at least
   one port.  The set of available ports represents a single
   SCA reference binding (i.e., it has multiplicity 1).  When an
   invocation is made using the SCA reference, the SCA runtime MUST use
   a port from the set of available ports for the reference (with port
   selection on a per-invocation basis permitted), or raise an error
   if the configurations of all the available ports prevent them from
   being used by the SCA runtime.

2) In the second bullet (Port) under the /binding.ws/@wsdlElement
description, replace all the current text by the following:

   If the binding is for an SCA service, the portType associated with
   the specified port MUST be compatible with the SCA service interface
   as defined in section 2.1, and the port MUST be able to satisfy all
   the policy constraints of the SCA service.  The SCA runtime MUST
   expose an endpoint for the specified port, or raise an error if
   the configuration of the port prevents it from being exposed by
   the SCA runtime.

   If the binding is for an SCA reference, the portType associated with
   the specified port MUST be a compatible superset of the SCA reference
   interface as defined in the SCA Assembly Model specification
   [SCA-Assembly], and the port MUST be able to satisfy all the policy
   constraints of the SCA reference.  The SCA runtime MUST use the
   specified port for invocations made using the SCA reference, or raise
   an error if the configuration of the port prevents it from being used
   by the SCA runtime.

3) In the third bullet (Binding) under the /binding.ws/@wsdlElement
description, replace the first two sentences of the current text by
the following:

   If the binding is for an SCA service, the portType associated with
   the specified WSDL Binding MUST be compatible with the SCA service
   interface as defined in section 2.1, and the WSDL Binding MUST be
   able to satisfy all the policy constraints of the SCA service.
   The SCA runtime MUST expose an endpoint for the specified WSDL Binding,
   or raise an error if the configuration of the WSDL Binding prevents it
   from being exposed by the SCA runtime.

   If the binding is for an SCA reference, the portType associated with
   the specified WSDL binding MUST be a compatible superset of the
   SCA reference interface as defined in the SCA Assembly Model
   specification [SCA-Assembly], and the WSDL binding MUST be able to
   satisfy all the policy constraints of the SCA reference.  The
   SCA runtime MUST use the specified WSDL Binding for invocations made
   using the SCA reference, or raise an error if the configuration of
   the WSDL Binding prevents it from being used by the SCA runtime.


4) Insert the following new section 2.1 and renumber the current
section 2.1 and subsequent sections.

   2.1 Compatibility of SCA Service Interfaces and WSDL portTypes

   A WSDL portType is compatible with an SCA service interface if and
   only if all of the following conditions are satisfied:
   1. The SCA service interface is remotable.
   2. The operations on the portType are the same as the operations
      on the SCA service interface, with the same operation name,
      same input types (taking order as significant), same output types
      (taking order as significant), and same fault/exception types.
      If the SCA service interface is not a WSDL portType, it is
      mapped to a WSDL portType for the purposes of this comparison.
      The mapping is defined in the relevant SCA specification for the
      interface type.  If the interface cannot be mapped to WSDL, the
      SCA service is not compatible with the WSDL portType.
   3. WSDL 1.1 message parts can point to an XML Schema element
      declaration or an XML Schema type.  When determining compatibility
      between two WSDL operations, a message part that points to an
      XML Schema element is considered to be incompatible with a
      message part that points to an XML Schema type.
   4. If either the portType or the SCA service interface declares
      an SCA callback interface, then both the portType and the
      SCA service interface declare callback interfaces and these
      callback interfaces are compatible according to points
      1 through 3 above.

   Simon