On Wednesday, January 8, 2003, at 09:32 AM, mati wrote:
I have been trying to use DefaultThreadManager from excalibur event package.
I just do not want to have an additional ThreadPool managed by
TPCThreadManager so I thought I would use the cornerstone one
The problem is that CornerStone uses old ThreadPool
import org.apache.avalon.excalibur.thread.ThreadPool;
which is depracated by now
On the other hand AbstractThreadManager expects to get the new one, and here
we have a problem
import org.apache.excalibur.thread.ThreadPool;
because I get exception:
org.apache.excalibur.containerkit.lifecycle.LifecycleException: Component
named "my-thread-manager" failed to pass through the Initialization stage.
(Reason: java.lang.IncompatibleClassChangeError).
I do not know what is the proper way of solving this problem. I've spotted
that Peter Donald created DefaultThreadManager (excalibur-event) so I am
wondering how did he manage to force these to work with Cornerstone
ThreadManager and it's ThreadPool.
I use the two together, but with an older snapshot of excalibur-event. -pete
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
