I figured out they still exist in spring-context [1].
I don't know what was going wrong...
What's about adding a Spring 3.2 feature so we can check whether we are
happy with this RC1 or whether we should raise last minute issues if our
build failed?
I will go ahead with this. Spring 3.1 will be st
Hi
Yeah we should use the ones from Camel.
Though I wonder where the Spring annotations was moved? Are they now
in a new JAR file in Spring 3.2 or where are they?
camel-spring is still depend on these annotations in its support for
these Spring annotations.
On Tue, Nov 13, 2012 at 12:08 AM, C
btw I also was confused which annotations to use, and after few experiments
I manged to make it work by using the spring annotations locally.
Also
http://camel.apache.org/why-is-my-processor-not-showing-up-in-jconsole.htmlsays
to use the spring annotations, not the Camel ones. Not sure what's the
I think we should not use the spring annotation for JMX export in camel.
That is why we define the same annotation in camel api.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://
org.apache.camel.processor.idempotent.jdbc.AbstractJdbcMessageIdRepository
is using org.springframework.jmx.export.annotation.ManagedResource and
org.springframework.jmx.export.annotation.ManagedOperation.
Shouldn't it be org.apache.camel.api.management.ManagedResource and
org.apache.camel.api.mana
