Re: cvs commit: avalon-excalibur/fortress/src/java/org/apache/avalon/fortress/impl/role AbstractRoleManager.java ConfigurableRoleManager.java

Peter Donald wrote:
> 
> any reason for making variable protected?

Yep.  I have need to extend this RoleManager with another one in the
GUIApp project.  If I can finish with that implementation I can make
the RoleManager work with @attributes.  I already have some ANT tasks
to make things work nicely.

It will be minimal, but a nicer first step away from ECM because
users will already be using meta data.

The two pieces of information I need to keep track of are:

Shorthand name (i.e. configuration alias)
Component Handler (i.e. lifestyle)

I would like us to discuss the name for expressing the lifestyle.

Of all the schemes that have been proposed so far, I like the one
that expresses lifestyle in terms of scope.

Scope     |   Lifestyle
----------+-----------------
Container | ThreadSafe
Thread    | PerThread
Request   | Pooled

There would be no direct mapping to the factory version--it would
have to be accessed via a fortress specific component-handler
attribute.

This is a far cry from Phoenix and Merlin's full component validation,
but it gets our users away from the explicit RoleManager paradigm and
more used to metadata.

I just need to finish what I am doing with it.