Thanks for your answer, but this is not really the thing I was looking for. ComponentHandler is a handler that is responsible for management of component "lifestyle", after it has already been created. What I'm looking for is some way to specify how to create the components...
Now I glanced over the AbstractComponentHandler class and found that it uses org.apache.excalibur.mpool.ObjectFactory implementation for component construction... would it be enough, if I just added a declaration for this role into my .roles file? Hmm, should check it out...
Neeme
Two things:
1) There is no way to override the ObjectFactory implementation through the .roles file.
2) The handler is what is used to govern how many instances of a component and when those instances are created.
The handler is specified in the <component/> section of the .roles file.
Now if you want to *extend* the avalon lifecycle with your own interfaces, then you can do that with the Lifecycle extention manager. Your interfaces will be called just before the Initializable interface on creation.
What problem are you trying to solve?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
