Build break in camel-jetty

Environmet: Apache Maven 2.2.1 (rdebian-4) Java version: 1.6.0_22 Java home: /usr/lib/jvm/java-6-openjdk/jre Default locale: en_GB, platform encoding: UTF-8 OS name: linux version: 2.6.38-8-generic arch: amd64 Family: unix Source: URL: https://svn.apache.org/repos/asf/camel/trunk Repository

Splitter StopOnException doesn't forward the exception on the Exchange

I have the following route which uses stopOnException to catch exceptions: route errorHandlerRef=queryFormularyError from uri=seda:createRx / split strategyRef=aggregatorStrategy parallelProcessing=true stopOnException=true method bean=processSegment method=split /

CustomAggregation of CSV not completing, don't want to complete using completionTimeout

I'm having trouble getting a slightly complex split/unmarshal/bean augment/aggregate pipeline to complete as I want it to. It completes with a completionTimeout set, but I want it to complete based on all messages from the batch getting through. Without the completionTimeout it hangs

Re: Using properties or headers to persist meta information on the exchange?

Hi Marco, have you tried 'transferExchange=true' inside your JMS route? That could be a solution for your JMS problem. Best regards - Claus On 08.06.2011 18:23, Marco Zapletal wrote: Hi, I learned from this thread

Re: Using properties or headers to persist meta information on the exchange?

Hi, thanks for the quick response. Yes, I've tried this, but this opens up another problem if you use a CXF endpoint on your route. The CXF endpoint seems to store an instance of org.apache.cxf.service.model.MessageInfo on the exchange, which is not serializable. This results in a runtime

Re: Using properties or headers to persist meta information on the exchange?

The JMS spec limits what can be send as JMS headers. Read more details on the Camel JMS wiki page. And for example in the JMS java doc. On Wed, Jun 8, 2011 at 6:36 PM, Marco Zapletal marco.zaple...@gmail.com wrote: Hi, thanks for the quick response. Yes, I've tried this, but this opens up

Re: Using properties or headers to persist meta information on the exchange?

Yes, I've read that. Actually, I just wanted to keep my (String) properties when the exchange goes through the JMS queue (similar like headers are kept over JMS queues). If it is the intended behavior that exchange properties are stripped away by the JMS component, I am fine with using

RE: Using properties or headers to persist meta information on the exchange?

Does that mean you can't count on your custom Camel message headers to survive a transition to JMS? -Original Message- From: Claus Ibsen [mailto:claus.ib...@gmail.com] Sent: 08 June 2011 19:41 To: users@camel.apache.org Subject: Re: Using properties or headers to persist meta

Stream is closed exception when calling CXF WS

Hi, When i call a CXF WS, an exception (Stream is closed) is thrown. In my search i have found a Jira, but i don't know if it's the same problem ? https://issues.apache.org/jira/browse/CXF-3554 Could you help me, or provide me way to analyse the problem ? Thanks Jérôme

file component: fileLock en preMove doesn't work

When using a file route with a preMove and a fileLock the move failes in windows: 2011-06-08 23:04:05,599 [Camel (camel) thread #0 - file:///camel] DEBUG org.apache.camel.util.FileUtil - Tried 3 to rename file: C:\camel\test3.txt to: C:\camel\tmp\test3.txt with result: false 2011-06-08

CXF + Camel + JMS Endpoint exception handling

I've started playing with CXF + Camel + JMS, and have set up a sample client and service that can put and get messages from a JMS Queue. I've started going deeper to understand the transaction and retry logic since one of the use cases I have is to use either the JMS or Camel retry logic to

Re: Stream is closed exception when calling CXF WS

Hi, It's a bug of CXF, you can work around it by changing the log level setting on the HTTPConduit. You can find more information here[1] [1]https://issues.apache.org/jira/browse/CXF-3466 On 6/9/11 2:23 AM, Jérôme Lelong wrote: Hi, When i call a CXF WS, an exception (Stream is closed) is

Re: CXF + Camel + JMS Endpoint exception handling

Current Camel transport for CXF just provides a transport tunnel for use to use. It can't handle the exception that comes from the service implementation. If you want the camel to handle the application exception, you may consider to use camel CXFBean[1] components. BTW you had to marshal the

Re: Using properties or headers to persist meta information on the exchange?

Marco, I think it depends on what you want to do. Of course there're components where you will loose message headers. Look at the file component, hazelcast:map or a database component. Of course you'll loose here the message headers, because they're bound to camel (where should you store them

Re: Build break in camel-jetty

Hi Yeah. We have not seen this error on the other OS. Do you get this error if you run the test multiple times? On Wed, Jun 8, 2011 at 9:21 AM, Jim Talbut jtal...@spudsoft.co.uk wrote: Environmet: Apache Maven 2.2.1 (rdebian-4) Java version: 1.6.0_22 Java home:

Redelivery, Attach Exception cause to message

Hi everybody, Just wanting to run some ideas about our design past the folks here and have a couple of questions from it. We are using ActiveMQ for our JMS We have a pretty simple processing pipeline where ... * Messages come in from various files * After small amount of filtering (different