mcconnell 2002/12/17 02:20:59 Modified: assembly STATUS-README-ITS-RELEVANT.TXT Log: Bringing the readme up-to-date. Revision Changes Path 1.2 +10 -5 avalon-sandbox/assembly/STATUS-README-ITS-RELEVANT.TXT Index: STATUS-README-ITS-RELEVANT.TXT =================================================================== RCS file: /home/cvs/avalon-sandbox/assembly/STATUS-README-ITS-RELEVANT.TXT,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- STATUS-README-ITS-RELEVANT.TXT 3 Dec 2002 06:58:17 -0000 1.1 +++ STATUS-README-ITS-RELEVANT.TXT 17 Dec 2002 10:20:58 -0000 1.2 @@ -1,18 +1,23 @@ -The avalon-sandbox/assembly package is a evolving in resoponse to discusions and ideas about profiles based containers thats been going on within the avalon-dev list recently. Much of the content here has been ripped out of the Avalon Excalibur Merlin packaged and refactored to be more more cleanly compoent based. The current result is a assembly/lifestyle/lifecycle management engine without any magic. The avalon-sandbox/merlin package is moving towards refactoring to leverage the assembly engine in the delivery of a dynamically deployed containers - you get exactly what you want for your containement problem - nothing more - nothing less. +The avalon-sandbox/assembly package is a evolving in response to discusions and ideas about profiles based containers thats been going on within the avalon-dev list recently. Much of the content here has been ripped out of the Avalon Excalibur Merlin packaged and refactored to be more cleanly component based. -There is still a lot of stuff to be done: +There is still a few things to be done: - * appliance manager is statically referncing the DefaultAppliance class - the objective it to have the assembly engine dynamically assembly the asembly implemetation class based on a comppontnt type addributute - but thins gets into some heavy nested assembly semantics + * revision of the context management to plug in context provider component that can be applied to a componet implementing the following operation pattern: + + void contextualize( <your-custom-context> ) throws ContextException; + + * review of the Appliance interface to support container specific supplimentation services, parameters and configuration on appliance creation. + + * getting service engine subsystem configuration in place - everything currently works without configuration which is nice for the dyncamic deployment scanarios, but getting full propergation of custom configuration will be a big plus in moving forward on the notion of profile driven containment - * getting subsystem configuration in place - everythig currently works without configuration which is noce for the dyncamic deployment scanarios, but getting full propergation of custom configuration will be a big plus in moving forward on the notriuon of profle diren containment To see the API in action: $ ant test -And you will see a bunch of test cases assemblying components with dependecies and all that soort of stuff. While component can have dynamic dependecies on the assembly system (i.e. a componet under asembly can may have a depedency which will be resolved by the assembly engine by calling the assembly engine to build the dependency), there is still work to be done on enabling the assembly engine to call itself to enable it to extend itself during its own assembly of itself. +And you will see a bunch of test cases assemblying components that basically work the service management engine for al of the variations. The avalon-sandbox/merlin package contains more comprehensive test cases that demonstrate the dynamic assembly of containers using the assembly sub-system. All contributions are really welcome!
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
