On Mon, 28 Oct 2002, at 08:16 [+0100], Stephen McConnell ([EMAIL PROTECTED]:
> I'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.
Just to make sure I'm following what you're saying, let me describe a
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. 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?
Gary
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
