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 <[email protected]> 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 > [email protected] > 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 > <[email protected]>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/ >> > > >
