Re: JMS as Dead Letter Channel in Transaction?

Hi You may want to use the DLQ built-in by AMQ instead. You can configure AMQ to do X number of redeliveries and if that fails move the message to a DLQ (either a shared or per destination DLQ). Then all that is done by AMQ, and you dont need to setup a DLQ error handler in Camel. What you want

Re: Proper way to override DefaultShutdownStrategy

Hi What do you want to do? If you want to do execute some custom code when CamelContext is being shutdown, then use event notifier, or the lifecycle strategy. Some links http://camel.apache.org/eventnotifier-to-log-details-about-all-sent-exchanges.html http://camel.apache.org/maven/current/camel

Re: Writing big files : stream or file ?

Hi, have a look at http://www.catify.com/2012/07/09/parsing-large-files-with-apache-camel/ - perhaps this helps (it's also about writing big files). Best regards - Claus On 01.05.2014 17:17, Ephemeris Lappis wrote: Hello. We have to produce some rather big volumes of data and generate outp

Re: Fastest Data Holder

Passing a JSON object across many processors can be costly too. Since the processors usually parse the object so that they can evaluate its value or add new values to it. I think for the case in the same JVM, it's OK to use Java objects like java.util.Map. On May 2, 2014 1:05 AM, "kraythe ." wrot

Re: About JAX-WS Holder NullPointerException

Update, I have spent some time reading the stacktrace calls, and found when CxfConsumer populate the parameters (inputMessage / MessageParts of type ArrayList) to the CamelExchange, the Holder is lost already. In the BidningOperationInfo object, it did has inputMessage(BindingMessageInfo type)/msg

Proper way to override DefaultShutdownStrategy

Hi all, I was looking for a way to have a shutdown callback. I overrode the doShutdown method of DefaultShutdownStrategy, thinking it would be called for shutdown of the camel context. Turns out that it's being called as a part of the shutdown for each route as well. Is there a more appropriate

Re: rsClient: successfully invoking REST service, but where is the response?

Sergey, Thank you for taking the time to respond. I'm not sure I understand your response. Again, my goal is to put together a series of camel routes that wire up a complete RESTful interaction with a remote web service, without writing any additional camel application code. The web service

About JAX-WS Holder NullPointerException

Hi All, I have just met the NullPointerException when dealing with the soap request input. The itnerface is like this @WebService(name="createSecurityOrder", targetNamespace="http://";) @XmlSeeAlso({ObjectFactory.class}) public interface CreateSecurityOrder { @WebResult(name = "Acknowledgme

Re: Fallback exception returned by camel 2.12

mvn dependency:tree is your friend. :) *Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Hardcore Java (2003) and Maintainable Java (2012)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 * On Thu, May 1, 20

Re: Fastest Data Holder

The question of efficiency should be thought of in an overall manner. Sure, the map is faster but when we add on all the serialization, is it really faster? JSON might be slower on access but the lack of needing to serialize it all the time has its benefits. This is important if the message will be

JMS as Dead Letter Channel in Transaction?

Anyone know how to configure JMS as a dead letter channel but in a transaction? Should be a simple issue I would think but its not working. final String fromURI = String.format("activemq:queue:%s?concurrentConsumers=%d", config.basicRouteInboxQueue(), config.concurrentConsumers()); er

Re: Fallback exception returned by camel 2.12

Thx. Kie-camel imported a different version of camel (2.10.3) while I was using 2.12.3 On Thu, May 1, 2014 at 6:06 PM, Claus Ibsen wrote: > Sounds like you got mixed versions of Camel on the classpath > > On Thu, May 1, 2014 at 5:18 PM, Charles Moulliard > wrote: > > Hi, > > > > My camel route

Re: Fallback exception returned by camel 2.12

Sounds like you got mixed versions of Camel on the classpath On Thu, May 1, 2014 at 5:18 PM, Charles Moulliard wrote: > Hi, > > My camel route testing Drools + Camel works fine with Camel 2.10 but when I > use Camel 2.12.x, I get this exception : > > 17:15:42.148 [main] DEBUG o.a.c.i.RouteService

Re: rsClient: successfully invoking REST service, but where is the response?

Hi This is the CxfRsproducer code I see may be related: // set response if (exchange.getPattern().isOutCapable()) { LOG.trace("Response body = {}", response); exchange.getOut().getHeaders().putAll(exchange.getIn().getHeaders()); exchange.getOut().setBody(binding.bindResponseToCamel

Fallback exception returned by camel 2.12

Hi, My camel route testing Drools + Camel works fine with Camel 2.10 but when I use Camel 2.12.x, I get this exception : 17:15:42.148 [main] DEBUG o.a.c.i.RouteService - Shutting down child service on route: testRoute -> Pipeline[[Channel[BeanProcessor[bean: personHelper]], Channel[sendTo(Endpoin

Writing big files : stream or file ?

Hello. We have to produce some rather big volumes of data and generate output files, in several steps, some of these steps using splitting to process inputs. I've been looking for two ways... The first way is writing a file, setting an "append" mode, that could be a nice solution to write batches

Re: Manually redeliver dead messages

Hi Marcus, I assume you already checked this out: https://camel.apache.org/error-handling-in-camel.html I am not sure what you mean with: „next version of the component“? A new version (e.g. improved parsing) of a bean? You could use a dead letter error handler (set the maximum redeliveries to 1