Hi, We had a debate on this topic. See:
http://osdir.com/ml/dev-tuscany.apache.org/2010-06/msg00164.html And apparently, we didn't reach agreement. I think it would be a good idea to agree on the commands for shell. This will help us understand how users use SCA. Then it can be translated into a set of API/SPIs. Mixing different steps into one layer could prevent us from seeing the complete user story. Raymond Feng Sent from my iPhone On Jul 7, 2010, at 11:53 PM, ant elder <[email protected]> wrote: > On Thu, Jul 8, 2010 at 7:14 AM, Jean-Sebastien Delfino > <[email protected]> wrote: > >> >> I'm confused as you've switched o.a.t.node.NodeFactory to a different >> o.a.t.node2.NodeFactory. I see 49 references to node.NodeFactory in the >> source tree, everywhere people need to create nodes. node2.NodeFactory looks >> like a parallel implementation, with only 3 references, if I'm not mistaken >> only from this new shell. What happened? >> > > The domain-node module is new is why its not used much yet and its > based more closely on the operations described in the Assembly spec. I > like it, and plan to start using it instead of the old Node APIs now. > It also supports more than the old Node API so you can do things that > you otherwise can't. > >> Also this new shell seems to use a single node. It's fine with me if that's >> what you want to do here, but that's not what I need. What I need is a >> collection of independent nodes, each loaded with a deployable composite, >> each with its own lifecycle, like I had in the original code. >> > > What is that you need a node for? This does give you independent > deployable composites each with its own lifecycle so whats missing? > I'm wondering if its just that the current commands and help > information on them isn't very clear yet so its not so obvious to you > what this is doing. > > ...ant
