Gary Shea wrote:
The scheme for specifying a LifestyleManager from the kernel.xml profile
is not quite ready for prime time.
An instance of DefaultLifestyleManager is set up
initially and attached to the KernelManager.
Yep.
This is the bootstrap lifestyle manager.
Then the kernel.xml configuration is checked for a lifestyle manager
specification, and if present, it is classloaded and semi-lifecycled.
It gets only enableLogging, configuration, initialization.
To properly set up DefaultLifestyleManager, contextualization with
the pool manager is needed.
Ok - this is possible - the lifestyle work was split acrsoss both myself
and Berin so it is feasible that there may be an inconsitency here. I'm
just sorting out some things on the type/service manager side and after
that I'll have take a look at the code so were in sysc.
I am not clear on how the second lifestyle manager ends up over-riding
the first one, but it does.
The lifestyle manager is supplied to the classloaders that are created
which means in principal that you will be able to customise lifestyle
handling at the level of a container. There is also the ability for a
component to declare a custom handler. As Berin has mentioned, some
refactoring is needed on the classloader - and the overall lifecycle and
lifestyle managers need to be abstracted out to an appliance manager.
This will make the code in the type/profile/lifecycle and lifestyle
area easier to work with.
Since the example kernel.xml from merlin
has the DefaultLifestyleManager specified in the kernel.xml file as the
LifestyleManager, the resulting setup is broken for pooling. Ironic,
since the DefaultLifestyleManager should work perfectly for pooling!
Umm, ... give me a couple of hours and I'll start digging.
Cheers, Steve.
Gary
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
