[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-assembly] Issue 183 - discussion and proposal
Snippet 7-2: binding.sca Pseudo-Schema
A binding.sca element has the attributes:
(0..1) - has the semantic:
– The @uri attribute can be omitted.
– If a <binding.sca/> element of a component reference specifies a URI via its @uri attribute, then this provides a wire to a target service provided by another component.
The form of the URI which points to the service of a component that is in the same composite as the source component is as follows:
– The circumstances under which the @uri attribute can be used are defined in section "Specifying the Target Service(s) for a Reference."
– For a binding.sca of a component service, the @uri attribute MUST NOT be present [ASM90005]
· name (0..1) – a name for the binding instance (an NCName), as defined for the base <binding/> element type.
· requires (0..1) - a list of policy intents. See the Policy Framework specification  for a description of this attribute.
· policySets (0..1) – a list of policy sets. See the Policy Framework specification  for a description of this attribute.
A binding.sca element has the child elements:
(0..1) - a wireFormat to apply to the data flowing using the binding.
binding.sca does not define any specific wireFormat elements.
· operationSelector(0..1) - an operationSelector element that is used to match a particular message to a particular operation in the interface. binding.sca does not define any specific operationSelector elements
The SCA binding can be used for service interactions between references and services contained within the SCA Domain.
The way in which this binding type is implemented is not defined by the SCA specification and it can be implemented in different ways by different SCA runtimes.
The only requirement is that any specified qualities of service are implemented for the SCA binding type. Qualities of service for <binding.sca/> are expressed using intents
and/or policy sets following the rules defined in the SCA Policy specification [SCA-POLICY].
The SCA binding type is not intended to be an interoperable binding type. For interoperability, an interoperable binding type such as the Web service binding is used.
An SCA runtime has to support the binding.sca binding type. See section 13.2.
A service definition with no binding element specified uses the SCA binding (see ASM50005 in section 4.2 on Component Service).
<binding.sca/> only has to be specified explicitly in override cases, or when a set of bindings is specified on a service definition and the SCA binding needs to be one of them.
If a reference does not have a binding subelement specified, then the binding used is one of the bindings specified by the service provider, as long as the intents attached to the reference and the service are all honoured, as described in Section 4.3 on Component Reference.
If the interface of the service or reference is local, then the local variant of the SCA binding will be used. If the interface of the service or reference is remotable, then either the local or remote variant of the SCA binding will be used depending on whether source and target are co-located or not.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
|From:||ashok malhotra <firstname.lastname@example.org>|
|To:||OASIS Assembly <email@example.com>|
|Subject:||[sca-assembly] Issue 183|
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU