A few comments: 1) Can we rename the package and class names? "something" and "Section10" seems to be strange :-).
2) The javadoc is difficult to read too with the line numbers copied from the spec. 3) I don't think the domain module should have any overlapping again the node modules. The domain provides functions to "manage" the SCA domain metadata through "deployment". The node is the execution environment for a group of top-level components from the SCA domain. IMO, Section10.java should NOT contain the getService() method. We could add methods to it so that it can be used to create NodeConfiguration though. An SCA domain has both metadata and runtime views. a. The SCA domain is the registry for contributions, composites, policy definitions and node configurations. The domain composite represents the overall composition of all the services that share the same boundary (wirings based on the SCA address) and vocabulary (policies). b. At runtime, the domain metadata is used by the nodes to execute the top-level components. The metadata can be made available to a node via a live domain registry (either centralized or distributed) or a set of offline configuration files. 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 Jun 5, 2010, at 12:20 AM, ant elder wrote: > Ok I've moved this to trunk now - > https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/domain/. > I really like these spec defined APIs, they make the use of > domains/contributions/composites much more explicit and seem more > intuitive than what we've currently got. We could carry on developing > them separately but that will result in some duplication with existing > code so it would be good to merge them with the existing Node code. > > ...ant
