I figured out - it was version mismatch with earlier version of spring from
other dependency.
I suppressed it with maven plug-in
org.apache.maven.plugins
maven-war-plugin
My Tomcat deployment of Camel 2.9 spring 3.6.0.Release got same exception,
may I know what calsspath configurations did you end up changing to fix
this?
Sep 5, 2013 8:48:05 AM org.apache.catalina.core.StandardContext
listenerStart
SEVERE: Exception sending context initialized event to listener ins
This seems to be our internal classpath configuration problem. Checked on a
clean environment and it actually works.
Anyway many thanks for quick support!
Dmitry
willem.jiang wrote:
>
> Hi,
>
> Which version of Spring 3.x are you using?
> I just checked the camel code with Spring 3.0.2 in th
On Fri, May 21, 2010 at 9:50 AM, Dmitry Buzdin wrote:
>
> 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.
>
Camel 2.x is compatible with Spring
Hi,
Which version of Spring 3.x are you using?
I just checked the camel code with Spring 3.0.2 in the eclipse, there is
no any complain about it.
As the TaskExecutor is extends the JDK's TaskExecutor.
Willem
Dmitry Buzdin wrote:
In latest release Spring dropped support of Java 1.4 and migra
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
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.
>
> Qu
