Gary Shea wrote:
If the component is managed by Merlin then if it is declared at assembly time (i.e. under a <container><component/> description) then it will be fully configured before the application et a reference to it. If you want to do dynamic addition then that's possible as well because you can build the defintion of the type and profile programatically as ask Merlin to depoly it for you. The "deployment service" I mentioned is the idea of taking this functionality and packaging under a service interface. This would/should make embedded use of Merlin easier to use and easier to understand.On Mon, 28 Oct 2002, at 08:16 [+0100], Stephen McConnell ([EMAIL PROTECTED]:Just to make sure I'm following what you're saying, let me describe aI'm currently refactoring a lot of CORBA related code to leverage Merlin - and I'm getting close to dealing with some similar stuff where there internal deployment of components (things like creating a new instance, setting the logger, context, initialization, etc.). But its basically hard-coding a lifecycle into the code which means two places to change if you make lifecycle updates. With the deployment service that should replaceable with a couple of lines and you will have complete assembly and lifestyle management for free.
situation which I think is similar and would benefit from a deployment
service.
I have a Swing app with a tabbed section. The number of tabs changes
depending on user creation of new orders, hiding of existing orders,
order deletion, recall of a hidden order, etc. The tabbed section is
an Avalon container (hopefully I'm using that term correctly...), but
configuration of a contained component cannot be assumed to occur at
startup.
Yes - it makes sence. I have web admin application which is doing something similar in that it is providing navigation of a Merlin container hierachy, the components each container contains, and the services published by the respective components. This is based on the current Merlin 2 package - the container is declared in a kernel.xml file together with enclosing components. I'm still playing somewhat with differnet attributes on components and services to facilitate MVC style management of content presentation.The contained components are the tabs, which are complex UI elements. I envision packaging up few context items (some of which will change with each deployment, as each tab has 'identity') and somehow handing them off to the deployment service, which then assembles the components that make up a tab. Makes sense?
Cheers, Steve.
Gary -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
-- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell@;osm.net http://www.osm.net -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
