Re: Notice of scheduled work

On Thu, 2003-07-17 at 22:25, Peter Donald wrote:
> Hi,
> 
> On Fri, 18 Jul 2003 07:49 am, Jason van Zyl wrote:
> > > I guess things got delayed. After the Avalon stuff disappears, is the
> > > idea that plexus users will create their own component interfaces and
> > > build a lifecycle around them, or will plexus have its own set of
> > > interfaces that define a different component lifecycle?
> >
> > The lifecycle is completely configurable. Dan is going to maintain the
> > Avalon container API which uses Avalon nomenclature. What I'm adding is
> > not going to be a whole lot different I'm just removing Avalon from the
> > core.
> 
> We were planning on doing something similar for loom. Essentially create a 
> lightweight stripped down framework similar to Avalon to use internally. 
> 
> Though we haven't really discussed it what I wanted to do was essentially take 
> best bits out of Avalon and rewrite them. In practical terms this meant
> 
> * Remove Version
> * Remove ExceptionUtil
> * Remove Cascading*
> * Remove Re* lifecycle stages
> * Remove all deprecated crapola
> * Merge Initializable/Disposable/Startable into interface "Active" or 
> something
> * Simplify implementations and put them in a separate package
> 
> Would you be interested in doing this together. To be honest I didn't want to 
> make it part of the public API or document it but it is not that much extra 
> work to get it as a free standing library.
> 
> Thoughts?

So this would be a library for lifecycle management essentially? If so
I'm sure we could wrangle something out. We could definitely make a base
tool and I was planning on using AspectJ to decorate and looks like
you've got XInvoke so this is definitely feasible.

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