avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <pe...@apache.org>
Subject RE: [Summary] Avalon 5 ComponentManager interface
Date Thu, 13 Jun 2002 00:14:10 GMT
At 11:03 AM 6/12/2002 -0400, you wrote:
>* The ComponentManager (should it be ComponentDirectory?) is used
>   by a client to gain access to other components.


+1000000000000000000000000000000000000000

The thing that is most confusing about Avalon is that the containers
>do things differently--and we need to unify the approach.  This is
>a _simplification_, not anything more complex.  Currently the way
>we represent meta-data is all over the place.  Fortress/ECM use a
>RoleManager, Phoenix uses component info (.xinfo) files, etc.


Slowly getting to something capable of representing what we need IMHO.
 >
> > For all its faults, A4 is *easy* to *use*. (Although I
> > confess I never ever understood the RoleManager.)
>
>
>Leo, the RoleManager is not a Framework thing--it is used in both
>ECM and Fortress.

Myrmidon also uses a RoleManager ;)


Cheers,

Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
              - John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message