[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [stp-dev] Service Creation questions
- From: "Beaurpere, David" <David.Beaurpere@xxxxxxxx>
- Date: Thu, 11 May 2006 10:44:20 +0100
- Delivered-to: firstname.lastname@example.org
- Thread-index: AcZzh9C24Pr/LCbYQlyZZ2mza+l08wBRN/Rg
- Thread-topic: [stp-dev] Service Creation questions
Actually I think that SC and SAF look
complementary: the Service Creation project intends to focus on
supporting existing service implementation tools while, and as far as I
understand it, SAF focuses on supporting tools that will manipulate the assembly
itself (graphical or otherwise).
SC is not about manipulating the
assembly, it aims at providing an integration layer for
existing service implementation tooling to integrate with with STP platform in
making the service implementations they produce available to the
assembly model (i.e. as componentType)
allowing change notification and synchronisations between the service
assembly tools and the various implementations tools it uses.
providing generic/convenience tools like a central assembly resources
view to help.
We do not really have more detailed requirements yet as we
need to work more with the SCA/STP framework and understand better what will be
needed. The plan is to acquire that understanding by 1st focusing on
developing an initial exemplary tool based on the Celtix runtime. So both
the Celtix tools and the SC platform will be worked on in
I am not clear about the role of
the Service Creation subproject. It seems like there may be some overlap
with the SOA Assembly Framework in the Core subproject. We need to ensure that
we are clear on the content in the subproject to avoid duplicate work.