What to do next for the Tuscany Java SCA 2.x stream

[Raymond Feng]

Hi,

I propose that we use the following two perspectives to drive the Tuscany 
Java SCA 2.x stream.

1) Runtime architecture: Clean up the core set of modules as documented at 
[1]
* Enforce the modularity and make sure cross-module code dependencies go 
through proper set of SPIs
* Rationalize the core-spi which is the contract between the core and 
extensions (implementations and bindings).

2) SCA functionality: Provide a consistent SCA domain story for deployment 
(See [2], [3] and [4]).

* Use scenarios to better understand how multiple contributions are 
installed to a SCA domain, how cross-contribution artifact references are 
resolved, how nodes are configured to represent runtime capabilities and how 
nodes run SCA composite applications.

* Decompose the basic services related to SCA domain management and provide 
SPIs for these atomic operations.

[1] 
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/OASIS+Development+Stream

[2] 
http://markmail.org/message/afae3zayzmpq6rx7?q=multiple+contributions+and+the+domain-level+composite&page=1&refer=qttcfwwun33gausl
[3] 
http://www.ibm.com/developerworks/opensource/library/ws-sca-tuscany/index.html
[4] 
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Distributed+Runtime

Thanks,
Raymond