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
--
Cheers,
Peter Donald
-----------------------------------------------
| If you turn on the light quickly enough, |
| you can see what the dark looks like. |
-----------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
