On Thu, Oct 1, 2009 at 11:49 AM, Raymond Feng <[email protected]> wrote: > I see the value to have a module/utility to process the contributions > without starting a runtime. The node runtime can call this utility to > load/build the contributions. Later on, the domain manager can leverage that > too. I anticipate the following layers: > > 1) Tuscany Kernel that sets up the extension point registry > 2) Tuscany Deployer that processes the contributions (We used to have a > workspace module that provides such capability) > 3) Tuscany Domain Manager that calls Tuscany deployer > 4) Tuscany Node that calls Tuscany deployer > > But I don't think this is the right approach by adding hard dependencies to > all the modules that contribute models and processors. Such modules should > be brought into the picture through the extension point/extension discovery. > The modules on the same layer are still subject to selections. A new > offering can be composed by picking needed modules from the layers and below > (like a subtree). >
+1 > IMO, bundling a set of modules should be addressed at a higher level with > the profile/feature idea. That lead to different packages of distributions > to download. I don't think there is a need to physically group modules (like > this scdl module) in the runtime. > +1 -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/
