Hello,
i've digged through some avalon usage in cocoon2, have the following
questions. can someone drop some thoughts?
1. why there're 2 DefaultComponentManager class impl in framework and
excalibur pkgs, isn't it confusing to some extent ?
2. it seems to me Cocoon class in Cocoon2 is a "container" class that imbed
a component manager. in this scenario, is it supposed to handle all the
lifecycles of components? i.e. instantiate component and populate them into
component manager ?
3. in component manager in excaliber pkg, what's difference btw
addComponent() and addComponentInstance() ?
4. who's responsible to the life cycle of component manager and role
manager? it seems to me container is.
5. who does componentmanager.release() do? according to javadoc, it
"release" component back. what if i don't release it? is it going to
"locked", i.e. it's a impl of single thread model ?
6. i see some benefit of using excalibur pkg. but if i don't use those
components, what's benefit of using framework pkg? i can basically define
similar interface and implement in my propriotary system and don't have to
spend time to dig into avalon framework apis.
7. what's component handler used for? i ran through some avalon src code, it
seems that lookup() -> role -> handler -> component within component
manager. i don't quite get why handler is being used ?
8. what's the concept of work interface? is it a real java interface or just
a concept in avalon component framework?
thanks in advance.
-sky
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
