I have a question as a newbie user of Avalon. Even though ComponentManager maybe is not the *perfect* name for what you want to achieve it is still used by all users of the Avalon framework isn't it? So why not keep the name so old users doesn't have to relearn or read the developer lists to understand what has happened to the ComponentManager. As documentation doesn't seem to be you're main interest this would probably save a lot of people a lot of grieve...
Imagine sun changing EJB to something else although meaning almost the same thing... I might have misunderstood the reason for the name change and in that case please disregard this mail. Cheers Fredrik -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
