Hi Terry!
Woden is considered an optional package. There may be an exception
logged at debug level, but it should not prevent the container from
booting. Woden is used in case some endpoints expose a WSDL 2.0
description.
The problem may just come from the fact that the PollingEndpoint puts
a runnable in the thread pool when the timer is firedintead of just
calling the poll method (I don't really see the reason why). Wanna
try with the following code in PollingEndpoint ?
private class PollSchedulerTask extends SchedulerTask {
public void run() {
try {
poll();
}
catch (Exception e) {
handlePollException(e);
}
}
}
On Sun, 21 Oct 2007 22:04 +0100 (BST), Terry Cox
<[EMAIL PROTECTED]> wrote:
> As has been reported previously by others, if you implement a component
> based upon PollingEndpoint then the poll method will be called more than
> once when the component starts.
>
> I have been investigating an example here and I can see that two
> different pool-components are running simultaneously in different threads.
> There also appear to be two Daemons, Timer-0 and Timer-1.
>
> I wondered if this were due to ServiceMix simply instantiating more than
> one instance of the component in a pool so I attempted to configure the
> executorFactory as shown in
> http://incubator.apache.org/servicemix/thread-pools.html to set the
> default pool size to 1.
>
> If I add the <sm:executorFactory> element to my config however, I get a
> java.lang.NoClassDefFoundError: org/apache/woden/WSDLReader early in the
> jbi config and the container fails to load. Any ideas?
>
> Terry
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
