[news.eclipse.stp.sca-tools] Re: Service term in SCA

[Stephane Drapeau <Stephane.Drapeau@xxxxxxx>]

You can easily add SAWSDL annotations on composite files with the 
Composite Designer [0].

Stephane

[0]: http://wiki.eclipse.org/STP/SCA_Project/Ontology

Stephane Drapeau a écrit :
> The SCA specifications don't address these problems.
> If a developer wants to be aware of the services already developed and 
> how to re-use them, then, a service repository or something like that is 
> needed.
> The SCOrWare project has developed a semantic trader [0] (page 65), 
> which, I think, can be an interesting solution. We can imagine using it 
>  at development time or at runtime.
>
> Stephane
>
> [0]: 
> http://www.scorware.org/projects/rsc/deliverables/SCOrWare-L1-Specifications-V2-0-20090414_pdf?action=download&nodecorator 
>
>
>
> Michael Gebhart a écrit :
> > Hi,
> >
> > thanks for your answer. I try to formalize my question in a differnt way:
> >
> > Assuming a distributed system developed with SCA (S1). We have 5 
> > components (A, B, C, D, E).
> >
> > Now, another system is developed, also with SCA (S2). It requires 
> > functionality that is already implemented in S1, more precisely 
> > component A and B.
> >
> > What happens? The developer who develops S2 does not know about A and 
> > B.  They are not provided as Webservice and are not registered within 
> > a service registry.
> >
> > How does the developer find A and B? Should A and B be exposed as web 
> > service from the beginning and published into a service registry?
> >
> > Or are they exposed as web service only on demand? But in this case: 
> > How does the developer know about A and B?
> >
> >
> > Next problem: A third system has to be developed, S3. It requires 
> > functionality that is part of S1, but not A, B, C, D or E.
> >
> > The developer of S1 declares himself ready to comply with exposing the 
> > required functionality as a component F. This can be used by S1 and S3.
> >
> > But there are other ways possible: F could also be part of S3 and S1 
> > uses this component as part of S3. Or should F be a completely new 
> > application? What is the right way to expose shared functionality?
> >
> >
> > Best regards
> >
> > Michael