Sorry guys, just found out that we can use ExecutorService as well and it is not actually a problem in our case. But the question of when you will migrate to Spring API version 3 is still actual.
Dmitry Dmitry Buzdin wrote: > > In latest release Spring dropped support of Java 1.4 and migrated custom > TaskExecutor API to JDK TaskExecutor. > > Dmitry > > > Dmitry Buzdin wrote: >> >> Hello, >> >> We are considering usage of Camel together with Spring 3.0. There is one >> API incompatibility, which blocks us from going forward. >> >> Question is whether Camel is meant to be compatible to 3.0 or still on >> 2.5 branch. The problem is that TaskExecutor related API changed in >> Spring 3 significantly, which results in NoSuchMethodError. >> >> java.lang.NoSuchMethodError: >> org.springframework.jms.listener.DefaultMessageListenerContainer.setTaskExecutor(Lorg/springframework/core/task/TaskExecutor;)V >> at >> org.apache.camel.component.jms.JmsConfiguration.configureMessageListenerContainer(JmsConfiguration.java:1072) >> at >> org.apache.camel.component.jms.JmsConfiguration.createMessageListenerContainer(JmsConfiguration.java:512) >> at >> org.apache.camel.component.jms.JmsEndpoint.createConsumer(JmsEndpoint.java:135) >> at >> org.apache.camel.component.jms.JmsEndpoint.createConsumer(JmsEndpoint.java:55) >> >> Regards, >> Dmitry Buzdin >> > > -- View this message in context: http://old.nabble.com/Camel-and-Spring-in-2.3-tp28630550p28630695.html Sent from the Camel Development mailing list archive at Nabble.com.
