You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/10/29 09:58:01 UTC

[jira] Resolved: (CAMEL-3286) camel-jms - Setting TaskExecutor should support both Spring 2.5 and 3.0

     [ https://issues.apache.org/activemq/browse/CAMEL-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3286.
--------------------------------

    Resolution: Fixed

We have introduced a new {{taskExecutorSpring2}} option you should use when using Spring 2.x with camel-jms.

trunk: 1028636.

> camel-jms - Setting TaskExecutor should support both Spring 2.5 and 3.0
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-3286
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3286
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.4.0, 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/camel-2-4-with-spring-2-5-6-TaskExecutor-issue-tp3237897p3237897.html
> We need to use reflection when invoking setTaskExecutor on the spring JMS stuff.
> Because at compile time it would be linked to the Spring 3.0 method signature.
> And in Spring 2.5 the method signature is different.
> Using reflection should allow us to support both cases. And this is only done on startup so no runtime overhead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.