[
https://issues.apache.org/activemq/browse/CAMEL-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47818#action_47818
]
tim mcnamara commented on CAMEL-1098:
-------------------------------------
I do not think there is a need, I was able to accomplish the adaptor with a
Spring proxy. something like this:
{code:title=Spring Proxied WorkManager}
<bean id="workManagerTaskExecutor"
class="org.springframework.jca.work.glassfish.GlassFishWorkManagerTaskExecutor"/>
<bean id="taskExecutor"
class="org.springframework.aop.framework.ProxyFactoryBean">
<property name="proxyInterfaces" value="java.util.concurrent.Executor"/>
<property name="target" ref="workManagerTaskExecutor"/>
<property name="proxyTargetClass" value="true"/>
</bean>
{code}
> multicast and file consumer using managed threads?
> --------------------------------------------------
>
> Key: CAMEL-1098
> URL: https://issues.apache.org/activemq/browse/CAMEL-1098
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.4.0, 1.5.0
> Reporter: tim mcnamara
> Assignee: Willem Jiang
> Fix For: 2.0.0
>
> Attachments: executor.patch, multicast.patch
>
>
> Running in a server managed environment, it is preferable to use managed
> threads when ever possible. Is it possible to have these components (and
> others that spawn threads) modified to use Spring's TaskExecutor abstraction
> (a la JmsComponent). If this is the case, we could configure the components
> to use the server's WorkManager API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
