OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: BINDINGS-23: Proposed resolution v4


As agreed on last week's call, here are two alternative versions
of the proposed resolution for BINDINGS-23.
. Option A permits wsdl.service for SCA service bindings, and
   requires the SCA runtime to make the service available on all
   matching ports or raise an error.
. Option B prohibits wsdl.service for SCA service bindings.

This difference only affects one portion of text, so the two
alternative wordings are shown for that portion only.  The rest
of the proposal is identical for both options.

Proposed Changes:

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

   - - - - - - - - - - - begin option A - - - - - - - - - - -
   If the binding is for an SCA service, the SCA runtime MUST make
   available to the SCA service all the ports in the WSDL Service that
   . have portTypes which are compatible with the SCA service as
     defined in section 2.1, and
   . are able to satisfy all the policy constraints of the SCA service.

   The WSDL Service MUST have at least one port that is available to
   the SCA service.  The set of available ports represents a single
   SCA service binding.  The SCA runtime MUST expose endpoints for
   all of the available ports, or raise an error if the configuration
   of any of the available ports prevents it from being exposed by
   the SCA runtime.
   - - - - - - - - - - - begin option B - - - - - - - - - - -
   If the binding is for an SCA service, the wsdlElement attribute
   MUST NOT specify the wsdl.service form of URI.
   - - - - - - - - - - - - end options  - - - - - - - - - - -

   If the binding is for an SCA reference, the SCA runtime MUST make
   available to the SCA reference all 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 WSDL Service MUST have at least one port that is available to
   the SCA reference.  The set of available ports represents a single
   SCA reference binding (i.e., it has multiplicity 1), and the choice
   of which of the available ports to use for an invocation on the
   SCA reference is made by the SCA runtime on a per-invocation basis.

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

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

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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]