tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raymond Feng" <enjoyj...@gmail.com>
Subject Re: [2.x] Calculating Endpoints to promoted services
Date Fri, 02 Oct 2009 15:46:24 GMT
The spec also has the following statement:

4917 B.10 Domain
4918 An SCA Domain represents a set of Services providing an area of 
Business functionality that is controlled
4919 by a single organization. As an example, for the accounts department in 
a business, the SCA Domain
4920 might cover all finance-related functions, and it might contain a 
series of composites dealing with specific
4921 areas of accounting, with one for Customer accounts, another dealing 
with Accounts Payable.
4922 A Domain specifies the instantiation, configuration and connection of a 
set of components, provided via
4923 one or more composite files. A Domain also contains Wires that connect 
together the Components. A
4924 Domain does not contain promoted Services or promoted References, since 
promotion has no meaning
4925 at the Domain level.

It's pretty clear that the promoted services/references at domain composite 
level should be ignored. We can produce a warning
if it helps.


From: "Simon Laws" <simonslaws@googlemail.com>
Sent: Friday, October 02, 2009 6:56 AM
To: <dev@tuscany.apache.org>; <antelder@apache.org>
Subject: Re: [2.x] Calculating Endpoints to promoted services

> Well we should either process it OR point out through a warning that
> it's being ignored. Silently ignoring it is what leads to confusion.
> What is the proposal to process? That we should assume that they
> configure the component references and services that they promote?
> From the example given it would seem that this is a valid way to
> configure a component service. However explicit words were put into
> the spec to apparently discount this at the domain leve. I'd like to
> get a sounding from one of the spec team on the implications of
> definition of composite services and references at the domain level as
> currently defined in the OASIS specs.
> On a purely technical note (which is probably not that relevant yet)
> we host service and reference endpoints and endpoint references on
> components. Composite services and references form part of the
> component type of a component that uses the composite through
> implementation.composite and hence that's where the endpoint and
> endpoint references are dealt with.
> Simon 

View raw message