You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Nirmal Fernando <ni...@gmail.com> on 2011/04/29 16:05:22 UTC
[GSoC] Artifacts of SCA
Hi,
Under my project Develop a simple tool that can be used to generate
composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
I need to identify all the possible artifacts that can be occurred in
a composite.xml file.
I already recognized following:
* Composite
* Component
* Property
* Reference
* Service
Is there any other artifacts I should consider? (other than the wire (link))
Thanks.
--
Best Regards,
Nirmal
C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.
Blog: http://nirmalfdo.blogspot.com/
Re: [GSoC] Artifacts of SCA
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi Jean,
On Sun, May 1, 2011 at 10:44 PM, Jean-Sebastien Delfino
<js...@apache.org> wrote:
> On 04/29/2011 07:05 AM, Nirmal Fernando wrote:
>>
>> Hi,
>>
>> Under my project Develop a simple tool that can be used to generate
>> composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
>> I need to identify all the possible artifacts that can be occurred in
>> a composite.xml file.
>>
>> I already recognized following:
>>
>> * Composite
>> * Component
>> * Property
>> * Reference
>> * Service
>>
>> Is there any other artifacts I should consider? (other than the wire
>> (link))
>>
> ...
>
> The SCA assembly specification [1] should give you a good idea of all the
> elements in a composite.
>
> The spec also describes a visual representation for these elements.
Thanks for the spec, that will be very helpful!
>
> What you have here is fine as a first step in my opinion.
I also prefer incremental development, for the time being I'll stick to those.
>
> Once you have that working, here are a few more, off the top of my head:
> - different implementation types
> - different binding types
> - composites nested in implementation.composite
> - promoted services, references and properties
> - includes
>
> Policies introduce yet another dimension so I'd suggest to look at them
> later as an option if you have time after completing the implementation of
> the above.
Thanks for these!
>
> [1] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-assembly
> --
> Jean-Sebastien
>
--
Best Regards,
Nirmal
C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.
Blog: http://nirmalfdo.blogspot.com/
Re: [GSoC] Artifacts of SCA
Posted by Jean-Sebastien Delfino <js...@apache.org>.
On 04/29/2011 07:05 AM, Nirmal Fernando wrote:
> Hi,
>
> Under my project Develop a simple tool that can be used to generate
> composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
> I need to identify all the possible artifacts that can be occurred in
> a composite.xml file.
>
> I already recognized following:
>
> * Composite
> * Component
> * Property
> * Reference
> * Service
>
> Is there any other artifacts I should consider? (other than the wire (link))
>
...
The SCA assembly specification [1] should give you a good idea of all
the elements in a composite.
The spec also describes a visual representation for these elements.
What you have here is fine as a first step in my opinion.
Once you have that working, here are a few more, off the top of my head:
- different implementation types
- different binding types
- composites nested in implementation.composite
- promoted services, references and properties
- includes
Policies introduce yet another dimension so I'd suggest to look at them
later as an option if you have time after completing the implementation
of the above.
[1] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-assembly
--
Jean-Sebastien
Re: [GSoC] Artifacts of SCA
Posted by Raymond Feng <en...@gmail.com>.
I'm not suggesting you to use the source code from the Graphviz project. We can just generate the .dot file from Java.
EPL is a compatible binary license for ASL, i.e, we can have binary dependencies on EPL artifacts.
Thanks,
Raymond
________________________________________________________________
Raymond Feng
rfeng@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
________________________________________________________________
On Apr 29, 2011, at 9:31 AM, Nirmal Fernando wrote:
> Hi,
>
> On Fri, Apr 29, 2011 at 9:53 PM, Raymond Feng <en...@gmail.com> wrote:
>> Hi,
>> For references/services, there are one or more bindings and one interface.
>> Node is not an SCA concept, it's Tuscany way to control the unit of work for
>> the runtime.
>> BTW, for the graphing, you can also look at a popular
>> tool http://www.graphviz.org/. It supports multiple layout algorithms and
>> the .dot file is a very simple text file that describes the graph (vertex,
>> edge). The Graphviz tool can export the .dot into most of the image formats.
>> One option for you is to generate the .dot from the composite.
>
> Is Eclipse Public License - v 1.0 compatible with Apache License?
>
> Thanks.
>> Thanks,
>> Raymond
>> ________________________________________________________________
>> Raymond Feng
>> rfeng@apache.org
>> Apache Tuscany PMC member and committer: tuscany.apache.org
>> Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
>> Personal Web Site: www.enjoyjava.com
>> ________________________________________________________________
>> On Apr 29, 2011, at 8:24 AM, Florian Moga wrote:
>>
>> Hi Nirmal,
>> Looking at the SCA plugin for Eclipse, I can see they also have
>> * Includes
>> * Intents / Policies
>> Other concepts which it would be good to consider are
>> * SCA Domain
>> * SCA Node
>> There is also an eventing spec that Tuscany doesn't support yet which
>> defines producers, consumers and channels. I don't think it's necessary to
>> support these now but you should probably consider an extensible design
>> which will allow adding them later.
>> Florian
>>
>> On Fri, Apr 29, 2011 at 5:05 PM, Nirmal Fernando <ni...@gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> Under my project Develop a simple tool that can be used to generate
>>> composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
>>> I need to identify all the possible artifacts that can be occurred in
>>> a composite.xml file.
>>>
>>> I already recognized following:
>>>
>>> * Composite
>>> * Component
>>> * Property
>>> * Reference
>>> * Service
>>>
>>> Is there any other artifacts I should consider? (other than the wire
>>> (link))
>>>
>>> Thanks.
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> C.S.Nirmal J. Fernando
>>> Department of Computer Science & Engineering,
>>> Faculty of Engineering,
>>> University of Moratuwa,
>>> Sri Lanka.
>>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
>
> --
> Best Regards,
> Nirmal
>
> C.S.Nirmal J. Fernando
> Department of Computer Science & Engineering,
> Faculty of Engineering,
> University of Moratuwa,
> Sri Lanka.
> Blog: http://nirmalfdo.blogspot.com/
Re: [GSoC] Artifacts of SCA
Posted by Nirmal Fernando <ni...@gmail.com>.
Hi,
On Fri, Apr 29, 2011 at 9:53 PM, Raymond Feng <en...@gmail.com> wrote:
> Hi,
> For references/services, there are one or more bindings and one interface.
> Node is not an SCA concept, it's Tuscany way to control the unit of work for
> the runtime.
> BTW, for the graphing, you can also look at a popular
> tool http://www.graphviz.org/. It supports multiple layout algorithms and
> the .dot file is a very simple text file that describes the graph (vertex,
> edge). The Graphviz tool can export the .dot into most of the image formats.
> One option for you is to generate the .dot from the composite.
Is Eclipse Public License - v 1.0 compatible with Apache License?
Thanks.
> Thanks,
> Raymond
> ________________________________________________________________
> Raymond Feng
> rfeng@apache.org
> Apache Tuscany PMC member and committer: tuscany.apache.org
> Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
> Personal Web Site: www.enjoyjava.com
> ________________________________________________________________
> On Apr 29, 2011, at 8:24 AM, Florian Moga wrote:
>
> Hi Nirmal,
> Looking at the SCA plugin for Eclipse, I can see they also have
> * Includes
> * Intents / Policies
> Other concepts which it would be good to consider are
> * SCA Domain
> * SCA Node
> There is also an eventing spec that Tuscany doesn't support yet which
> defines producers, consumers and channels. I don't think it's necessary to
> support these now but you should probably consider an extensible design
> which will allow adding them later.
> Florian
>
> On Fri, Apr 29, 2011 at 5:05 PM, Nirmal Fernando <ni...@gmail.com>
> wrote:
>>
>> Hi,
>>
>> Under my project Develop a simple tool that can be used to generate
>> composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
>> I need to identify all the possible artifacts that can be occurred in
>> a composite.xml file.
>>
>> I already recognized following:
>>
>> * Composite
>> * Component
>> * Property
>> * Reference
>> * Service
>>
>> Is there any other artifacts I should consider? (other than the wire
>> (link))
>>
>> Thanks.
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> C.S.Nirmal J. Fernando
>> Department of Computer Science & Engineering,
>> Faculty of Engineering,
>> University of Moratuwa,
>> Sri Lanka.
>> Blog: http://nirmalfdo.blogspot.com/
>
>
>
--
Best Regards,
Nirmal
C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.
Blog: http://nirmalfdo.blogspot.com/
Re: [GSoC] Artifacts of SCA
Posted by Florian Moga <mo...@gmail.com>.
Hi Raymond,
Thanks for clarifying the Node terminology. Useful to know it's not part of
the SCA specs.
Another suggestion, if there will be domain support it will probably be nice
to display promotion of services, references, properties, etc. as well. What
do you think? We can keep that towards the end of the project if there's
enough time left.
Florian
On Fri, Apr 29, 2011 at 7:23 PM, Raymond Feng <en...@gmail.com> wrote:
> Hi,
>
> For references/services, there are one or more bindings and one interface.
> Node is not an SCA concept, it's Tuscany way to control the unit of work for
> the runtime.
>
> BTW, for the graphing, you can also look at a popular tool
> http://www.graphviz.org/. It supports multiple layout algorithms and the
> .dot file is a very simple text file that describes the graph (vertex,
> edge). The Graphviz tool can export the .dot into most of the image formats.
> One option for you is to generate the .dot from the composite.
>
> Thanks,
> Raymond
> *________________________________________________________________
> Raymond Feng
> rfeng@apache.org
> Apache Tuscany PMC member and committer: tuscany.apache.org
> Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
> Personal Web Site: www.enjoyjava.com
> ________________________________________________________________*
>
> On Apr 29, 2011, at 8:24 AM, Florian Moga wrote:
>
> Hi Nirmal,
>
> Looking at the SCA plugin for Eclipse, I can see they also have
> * Includes
> * Intents / Policies
>
> Other concepts which it would be good to consider are
> * SCA Domain
> * SCA Node
>
> There is also an eventing spec that Tuscany doesn't support yet which
> defines producers, consumers and channels. I don't think it's necessary to
> support these now but you should probably consider an extensible design
> which will allow adding them later.
>
> Florian
>
>
> On Fri, Apr 29, 2011 at 5:05 PM, Nirmal Fernando <ni...@gmail.com>wrote:
>
>> Hi,
>>
>> Under my project Develop a simple tool that can be used to generate
>> composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
>> I need to identify all the possible artifacts that can be occurred in
>> a composite.xml file.
>>
>> I already recognized following:
>>
>> * Composite
>> * Component
>> * Property
>> * Reference
>> * Service
>>
>> Is there any other artifacts I should consider? (other than the wire
>> (link))
>>
>> Thanks.
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> C.S.Nirmal J. Fernando
>> Department of Computer Science & Engineering,
>> Faculty of Engineering,
>> University of Moratuwa,
>> Sri Lanka.
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
Re: [GSoC] Artifacts of SCA
Posted by Raymond Feng <en...@gmail.com>.
Hi,
For references/services, there are one or more bindings and one interface. Node is not an SCA concept, it's Tuscany way to control the unit of work for the runtime.
BTW, for the graphing, you can also look at a popular tool http://www.graphviz.org/. It supports multiple layout algorithms and the .dot file is a very simple text file that describes the graph (vertex, edge). The Graphviz tool can export the .dot into most of the image formats. One option for you is to generate the .dot from the composite.
Thanks,
Raymond
________________________________________________________________
Raymond Feng
rfeng@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
________________________________________________________________
On Apr 29, 2011, at 8:24 AM, Florian Moga wrote:
> Hi Nirmal,
>
> Looking at the SCA plugin for Eclipse, I can see they also have
> * Includes
> * Intents / Policies
>
> Other concepts which it would be good to consider are
> * SCA Domain
> * SCA Node
>
> There is also an eventing spec that Tuscany doesn't support yet which defines producers, consumers and channels. I don't think it's necessary to support these now but you should probably consider an extensible design which will allow adding them later.
>
> Florian
>
>
> On Fri, Apr 29, 2011 at 5:05 PM, Nirmal Fernando <ni...@gmail.com> wrote:
> Hi,
>
> Under my project Develop a simple tool that can be used to generate
> composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
> I need to identify all the possible artifacts that can be occurred in
> a composite.xml file.
>
> I already recognized following:
>
> * Composite
> * Component
> * Property
> * Reference
> * Service
>
> Is there any other artifacts I should consider? (other than the wire (link))
>
> Thanks.
>
> --
> Best Regards,
> Nirmal
>
> C.S.Nirmal J. Fernando
> Department of Computer Science & Engineering,
> Faculty of Engineering,
> University of Moratuwa,
> Sri Lanka.
> Blog: http://nirmalfdo.blogspot.com/
>
Re: [GSoC] Artifacts of SCA
Posted by Florian Moga <mo...@gmail.com>.
Hi Nirmal,
Looking at the SCA plugin for Eclipse, I can see they also have
* Includes
* Intents / Policies
Other concepts which it would be good to consider are
* SCA Domain
* SCA Node
There is also an eventing spec that Tuscany doesn't support yet which
defines producers, consumers and channels. I don't think it's necessary to
support these now but you should probably consider an extensible design
which will allow adding them later.
Florian
On Fri, Apr 29, 2011 at 5:05 PM, Nirmal Fernando <ni...@gmail.com>wrote:
> Hi,
>
> Under my project Develop a simple tool that can be used to generate
> composite diagrams https://issues.apache.org/jira/browse/TUSCANY-3496
> I need to identify all the possible artifacts that can be occurred in
> a composite.xml file.
>
> I already recognized following:
>
> * Composite
> * Component
> * Property
> * Reference
> * Service
>
> Is there any other artifacts I should consider? (other than the wire
> (link))
>
> Thanks.
>
> --
> Best Regards,
> Nirmal
>
> C.S.Nirmal J. Fernando
> Department of Computer Science & Engineering,
> Faculty of Engineering,
> University of Moratuwa,
> Sri Lanka.
> Blog: http://nirmalfdo.blogspot.com/
>