On Sunday 14 December 2003 04:01, David Le Strat wrote:
> <quote>
>
> > 2. Or do you have a component written that expects
> > to be in a Merlin container
> > and you just want to use that component completely
> > without Merlin?
>
> </quote>
Not only do you have to look at the complexity of the overall system, but also
the "expectation" of the component.
1. Is it Contextulizable? If so, what context entries does it expect?
2. Is it Configurable? If so, what configuration does it expect?
3. Does it has any dependencies? If so, what are they, and how do I
instantiate them (typically the same way).
If the answers to those questions are "No", then it is just a matter of
hardcoding the LifeCycle;
MyComponent c = new MyComponent();
if( c instanceof LogEnabled )
c.enableLogging( logger );
if( c instanceof Initializable )
c.initialize();
and so on...
Alternatively, and possibly recommended, again slightly depending on the
overall system;
Embed Merlin into your app. I haven't been working with this yet (brand new
concept).
If you look at the bootstrapper in avalon/repository, I think you can get an
idea. Not sure if there are some helper classes to make it less painful.
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
