Berin Loritsch wrote:
>>From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
>>
>>Marcus Crafter wrote:
>>
>>
>>
>>>Hi Stephen,
>>>
>>> Sorry, I'm coming into the thread a little late - I'll
>>>
>>>
>>have a look at
>>
>>
>>> what you've done in Merlin below and send in some comments soon.
>>>
>>>
>>>
>>>
>>Great!
>>I'm looking forward to ticking that one off the list,
>>
>>
>
>
>Me too!
>
>
>
>>> Are you in the process of splitting up the jar files now ?
>>>
>>>
>>>
>>If you happy with the org.apache.ezcalibur.container.lifecycle stuff
>>(inside the excalibur/assembly CVS), I'll package it up into
>>a seperate
>>jar file ASAP.
>>
>>
>
>I am happy with it.
>
>
>
>
>>> Assuming the extension models are now consolidated -
>>>
>>>
>>the next thing in
>>
>>
>>> the lifecycle extension world to look at was the
>>>
>>>
>>session proposal
>>
>>
>>> from Berin, archived under
>>>
>>>
>>>
>>http://marc.theaimsgroup.com/?l=avalon-dev&m=102742811501755&w=2.
>>
>>
>>>
>>> Have you investigated this one already ?
>>>
>>>
>>>
>>>
>>Nope - I actually want to finalize the lifestyle content
>>first (any help
>>from Fortress people appraciated).
>>
>>
>
>That's cool. I want a common model as well.
>
>
>
>> Basically singleton and transient
>>are in place. Getting in mpool based pooled policy and
>>per-thread would
>>wrap that item up nicely. Fro there I would like to do a
>>review of the
>>meta model package - make sure all the doc is ok, check
>>consistency in
>>method naming, class naming etc. then push this into a
>>seperate project.
>> After that, update Merlin 2.0 to use the "common" meta-model
>>and get an
>>alpha release out the door.
>>
>>
>
>What help do you need?
>
What I would like to do is to put in place a pooled and per-thread
handler. I've got the framework in place but I really don't know
anything about the mpool stuff. What would be perfect is someone who
knows mpool and Fortress inside out, and is keen to learn about the
Merlin meta API, and wants to volunteer to put something in place (hint,
hint) ;-). I've done transient and singleton as examples of using the
lifestyle manager and abstract lifestyle handler. In addition I've put
in place a framework which will allow replacement of the lifestyle
manager at a per-container level which means potential assignment of a
Fortress manager to a container and from there a specialized container
(e.g. Fortress can do whatever it wants inside Merlin) running parrallel
with Merlin containers.
Cheers, Steve.
>
>
>
>--
>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]>
