On Wed, Dec 9, 2009 at 3:09 PM, Simon Laws <[email protected]> wrote:
>> >> - it would useful and consistent to have a way to use Nodes with the >> objects created from the Deployer so for example you can doing things >> like Deployer.loadContribution, fiddle about with the Contribution and >> then use that object in a Node. I'm not suggesting a method signature >> for this yet as this opens up quite a lot of interesting options. For >> example, all the NodeFactory methods about attaching or adding >> deployment composites could then be done via the Deployer instead of >> all the overloaded createNode methods. To do this well requires quite >> a lot of changes to the Node APIs but after some playing around it >> looks to me like it could make the APIs much cleaner with the simple >> uses clear and obvious and the more complex cases more consistent and >> powerful. > > Interesting. Sounds like you have examples. Can you post? Need to be > careful about dependencies, i.e. to use the API what dependencies do > you need to include. We have a workspace manager in 1.x that combines > deployer type features with the ability to interact with the > runtime/exntrsion points. No precisely what you are suggesting but I > remember there were a lot of dependencies. Let discuss more and see > where it goes. > I could add some code to show it, but before I do can you say more about what the dependencies might be? The only dependency issues i can think of are being able to use the Deployer without dragging in the whole runtime but thats not an issue for Node, AFAIR all the workspace stuff was removed as we just didnt have any use cases for the functions it provided. ...ant
