Re: Multiple lifecycles per container

On Thu, 2003-07-24 at 19:59, Bert van Brakel wrote:
> Sorry I've been out of touch. Got caught up in one of my projects. 
> 
> The patch allows one to specify a default instantiation strategy and
> lifecycle handler, being capable of being overridden per component.
> 
> The plexus default is an avalon lifecycle handler with the classical
> singlton, as per currently.
> 
> I'll upload the patch to jira today. Haven't had time to fully write the
> tests as I was hoping, but I'll get round to it once I have a few other
> problems sorted out first.
> 
> The big patch is probably not so big. Basically it's just this.

Cool, I'll write some tests for it while I integrate the patch.

> Anyway, see jira in a  couple of hours.
> 
> -bert
> 
> On Fri, 2003-07-25 at 03:56, Jason van Zyl wrote:
> > Howdy,
> > 
> > I'm not sure where Bert is but I think he's already done the work to do
> > this. Bert if you are around and you can separate that bit out of your
> > massive patch I will integrate that as I do think that is useful now.
> > Previously I was think of limiting a set lifecycle to a container but I
> > don't really see any downside to not allowing components to do different
> > things inside the same container.
> > 
> > Which leads me into the next thing which is a little configuration
> > change that would allow a component profile of sorts. So in a profile
> > you could specify a default lifecycle and instantiation strategy for a
> > component and just use the profile id in the component configuration. As
> > well there could just be a default component profile.
> 
> _______________________________________________
> Plexus-dev mailing list
> [email protected]
> http://lists.codehaus.org/mailman/listinfo/plexus-dev
-- 
jvz.

Jason van Zyl
[email protected]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society