Thanks a lot. It works now.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-2-4-with-spring-2-5-6-TaskExecutor-issue-tp3237897p4933214.html
Sent from the Camel - Users mailing list archive at Nabble.com.
>From Camel 2.7+ onwards, Spring 3+ is required.
See release notes
http://camel.apache.org/camel-270-release.html
On Mon, Oct 24, 2011 at 5:56 PM, ebinsingh
wrote:
> Hi, Is this issue resolved.
>
> Please advise.
>
> I am using the following versions
> Camel: 2.8.1
> Spring: 2.5.6
>
> I am just
Hi, Is this issue resolved.
Please advise.
I am using the following versions
Camel: 2.8.1
Spring: 2.5.6
I am just trying to consume messeges on a queue write it on a SEDA. But I
get the following error.
context.addRoutes(new RouteBuilder() {
public void conf
Hi
I have created a ticket to track this bug
https://issues.apache.org/activemq/browse/CAMEL-3286
Lets see if we can get it to support both out of the box.
On Wed, Oct 27, 2010 at 5:13 PM, Claus Ibsen wrote:
> On Wed, Oct 27, 2010 at 3:52 PM, ndjensen wrote:
>>
>> We are using an instance of
We are using an instance of
org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor and setting
it on the JmsComponent.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-2-4-with-spring-2-5-6-TaskExecutor-issue-tp3237897p3238749.html
Sent from the Camel - Users ma
Are you using a custom TaskExecutor?
Have you configured the JMS component/endpoint to use a custom TaskExecutor?
I would assume if you do NOT do this then it should work as it wont
invoke that method.
On Wed, Oct 27, 2010 at 12:14 AM, ndjensen wrote:
>
> Hi, we're upgrading from camel 2.2 to 2
Hi
Ah good catch. Looks like a non backward comb. change by Spring :(
The JAR is build against Spring 3.0.
You can build against Spring 2.5.6 as documented here
http://camel.apache.org/building.html
On Wed, Oct 27, 2010 at 12:14 AM, ndjensen wrote:
>
> Hi, we're upgrading from camel 2.2 to 2
Hi, we're upgrading from camel 2.2 to 2.4 but are staying with Spring 2.5.6
for the time being. At startup of our application we receive the following
error:
Caused by: java.lang.NoSuchMethodError:
org.springframework.jms.listener.DefaultMessageListenerContainer.setTaskExecutor(Ljava/util/concur