Multiple lifecycles per container

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.

-- 
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