When you say "latest version", is that 2.0.4, or a dev build? I am using 2.0.4 right now. It seems like the CocoonComponentManager delegates to ExcaliburComponentManager. Also, the Cocoon.java class uses ExcaliburComponentManager to load components from the cocoon.xconf (which is where I put my task manager component).
I was going to copy the class and switch from Servicable, to Composable, but I needed to be in the same package. I just added ComposableComponentManager with the change into the excalibur.jar. I figured whatever I did would be transitional until I use a later version of cocoon.
BTW, Now, I find that my component is being disposed right after it gets configured/composed/started. Do I need to make it a daemon?
Thanks!
David
Peter Donald wrote:
On Sat, 5 Apr 2003 02:23, David Kavanagh wrote:
It looks like the Avalon team has shifted from components to services
and cocoon is stuck on components still.
The latest version of Cocoon can support either IIRC.
Because of the time scheduling code, I need to have the thread manager configured, but it is written to be "servicable". So, my problem is that I can't get the thread manager going in the cocoon environment and some of my code blows up when the DefaultTimeScheduler can't lookup the thread manager.
Any thoughts or suggestions?
If you are stuck on that version of Cocoon then you can do a couple of things. Firstly you could exten the classes like
class MyTimeScheduler implements Composable { void compose( ComponentManager cm ) throws ComponentException { try { service( new WrapperServiceManager( cm ) ); } catch ( final ServiceException se ) { throw ComponentException( se.getKey(), se.getMessage(), se.getCause() ); } } }
or just directly copy the source into your own trewe
