Hi Dan,
Thanks for your inputs, these help user to configure the executor
better, I will commit these enhancements shortly.
Willem
On 4/29/11 9:41 PM, Daniel Kulp wrote:
Willem,
I think there needs to be two "enhancements" to this before it's really
finished:
1) JAX-WS provides API's for setting an Executor to use on the clients. I
think it would be best to use that Executor if the user has set it. I think
that's pretty easy as I think it saves it on the Exchange
(message.getExchange().get(Executor.class)). Not 100% sure on that, but I
think that's it.
2) If the user hasn't set one, it would be good to check for a configured
named workqueue before grabbing the default workqueue. We do this in JMS if
you need an example. For example, they could configure a workqueue
specifically for a named service. If not, maybe just look for a workqueue
named "local.transport.default". Then use the default. That allows some
level of local configuration and isolation from the rest of the stuff running.
Definitely not a -1 on this commit, but I think the above two issues should be
addressed as part of this new functionality.
Dan
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Connect at CamelOne May 24-26
The Open Source Integration Conference
http://camelone.com
