Re: Camel 2.10.2 timer component does not fire at startup

Thanks Claus, I tried this, but it didn't work. I tried both with delay and initialDelay. This wasn't happening with previous versions of Camel, this is why I'm writing here. Besides, it wouldn't explain why, after a manual stop/start of the route via JMX, the timer fires right after the route

Re: onException vs. doTry...doCatch

/lug/2011, alle ore 13.45, Claus Ibsen-2 [via Camel] ha scritto: On Fri, Jul 15, 2011 at 1:41 PM, alberto.zigoni [hidden email] wrote: I am trying to properly configure error handler with onException on this route: route id=cashReservationsRoute handleFault=true from uri

two webapps on Tomcat sharing cache through Camel

I have defined a Camel context with a route creating and populating a cache. This camel context is included into a web application deployed on Tomcat. The route creating and populating the cache is fired at startup using a Quartz endpoint. Everything works fine. Now I want to query that cache

Re: two webapps on Tomcat sharing cache through Camel

] ha scritto: Maybe just copy that camel-cache JAR into tomcat shared lib. And then keep the other Camel JARs in your WARs. On Mon, Jul 18, 2011 at 9:42 AM, alberto.zigoni [hidden email] wrote: I have defined a Camel context with a route creating and populating a cache

Re: two webapps on Tomcat sharing cache through Camel

/2011, alle ore 10.26, Claus Ibsen-2 [via Camel] ha scritto: On Mon, Jul 18, 2011 at 10:21 AM, alberto.zigoni [hidden email] wrote: Claus, I have tried it first, but there are a lot of ClassNotFoundError problems. Even though you find the least amount of jars to be copied

onException vs. doTry...doCatch

I am trying to properly configure error handler with onException on this route: route id=cashReservationsRoute handleFault=true from uri=direct:startCashReservationsRoute / onException exceptionorg.apache.cxf.interceptor.Fault/exception

Re: Warning in cxf endpoint configuration

Hi Willem, I confirm that 2.8-SNAPSHOT solves the problem. Alberto -- View this message in context: http://camel.465427.n5.nabble.com/Warning-in-cxf-endpoint-configuration-tp4561812p4564027.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Unable to marshal type org.hl7.v2xml.ORUR01CONTENT as an element because it is missing an @XmlRootElement annotation

It seems like you haven't set the partNamespace corresponding to the partial class. dataFormat.setPartNamespace(new QName(...)); -- View this message in context:

Multiple contexts startup order with Spring

Is it possible to define the order in which different Camel contexts should be started, using Spring? One solution could be to set autoStartup=false to each context and then having a Spring context-aware bean perform the startup of the contexts in the right order, but I am looking for an

Re: Multiple contexts startup order with Spring

Using depends-on on the camelContext does the trick, but it couples the contexts. In my case, the first context is used only during development. Anyway, I have just found a rather rough but working way of doing it. My Camel contexts are defined in two different XML files under META-INF/spring,

Warning in cxf endpoint configuration

I am using camel 2.6.0 and have configured a cxf endpoint like this: cxf:cxfEndpoint id=dgwEndpoint address=http://localhost:9090/my/mockServices; wsdlURL=classpath:wsdl/my.wsdl serviceClass=com.acme.BusinessServicePort

Re: camel-cache: NPE for operations not requiring key

@Willem: version 2.7.2 solves the problem. @Ashwin: this is the stacktrace I get using 2.6.0: [efaultQuartzScheduler_Worker-1] DefaultErrorHandlerERROR Failed delivery for exchangeId: ID-localhost-64937-1309854451521-0-2. Exhausted after delivery attempt: 1 caught:

Re: camel-cache: NPE for operations not requiring message body

Subject was wrong, sorry. -- View this message in context: http://camel.465427.n5.nabble.com/camel-cache-NPE-for-operations-not-requiring-key-tp4549468p4550069.html Sent from the Camel - Users mailing list archive at Nabble.com.