Peter Donald wrote:
>
> Hi,
>
> The current org.apache.avalon.component.Default* is Cocoon specific. It
> links against org.apache.excalibur.pool.* and uses format specified in
> Cocoon conf file. This is problematic considering the framework classes are
> meant to be independent of components. Consequently I propose that we move
> the classes either into excalibur or cocoon. We can rework the
> RoleManager/Other to be more generic (not deal with
> threading/pooling/whatever) and keep that in avalon.component.*. We then
> move the hashtable based DefaultComponent* into org.apache.avalon.component.*
I could have sworn I got rid of the Cocoon specificity. You have a role
manager that takes care of the named configurations, etc.
Ok. Move it to Excalibur. The Component framework that is there now in Avalon,
shouldn't even mention Cocoon, and it takes care of alot of lifecycle issues
for you. Personally, I'd like to see more of you using it. They were moved
into Avalon, because they were written in a manner where they could be used
in any project. The move was to give people a more pleasant experience in
programming for Avalon--not just Cocoon.
Besides, What's wrong with using the new framework? You can add regular
components and it acts like the previous ComponentManager, or it can
create Components on demand. It depends on what you want to do with it.
It's flexible enough to let it be dumb or smart.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
