Hello,
On the destination side, is incomingObserver.onMessage(msg) supposed to queue
up the msg and have a thread pool handle the message? I noticed in the log
that, sometime, the implementation is invoked by the same thread that called
onMessage. And at other times, I see "default-workqueue-#" with # being a
number.
Anyone knows why my thread id would show up in the log inside the function
being invoked. I expected it to be a thread with a "default-workqueue-#" id.
Thanks,
public class MyDestination
extends AbstractMultiplexDestination
{
public void process(MyMessage myMessage)
{
Message cxfMsg = transform(myMessage);
BusFactory.setThreadDefaultBus(bus);
incomingObserver.onMessage(cxfMsg);
}
}
