sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: [ISSUE 143] There are no conformance statements in section 8.5 (CD03) -Updated Proposal
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: "OASIS Assembly" <sca-assembly@lists.oasis-open.org>
- Date: Tue, 27 Oct 2009 13:40:21 +0000
Here is an updated proposal to resolve
Issue 143
- the following text is a complete replacement
for section 8.5:
8.5 SCA Binding
The SCA binding element is defined by
the following schema.
<binding.sca />
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.
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.
If a <binding.sca/> element which
is a subelement of a <component/> <reference/> element 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 for a wire to the
service of a component which is in the same composite as the component
with the reference is:
· <component-name>/<service-name>
Yours, Mike.
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
Email: mike_edwards@uk.ibm.com
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
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
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]