Re: What happens to Exchange's exception in DeadLetterChannel?

On Wed, Aug 31, 2011 at 11:41 AM, Claus Ibsen wrote: > > Thanks I have updated both pages. Thank _you_. > You are welcome to send in an ICLA to Apache, so you in the future > will be able to edit the documentation, and contribute to the project. > Its also one step closer to be a committer, as a

Re: What happens to Exchange's exception in DeadLetterChannel?

On Wed, Aug 31, 2011 at 10:59 AM, Claus Ibsen wrote: > On Wed, Aug 31, 2011 at 4:34 PM, David Tombs wrote: >> Hi there, >> >> I'm using a Dead Letter Channel error handler and am a little confused >> about what happens to the original Exception while on the dead l

What happens to Exchange's exception in DeadLetterChannel?

Hi there, I'm using a Dead Letter Channel error handler and am a little confused about what happens to the original Exception while on the dead letter queue. - Camel In Action says that it's stored in the 'Exchange.CAUSED_EXCEPTION' property, which doesn't seem to exist (p127). - DeadLetterChanne

custom MDC property

Hello Camel Folks, I'd like to add an MDC property to our logs that is generated from a few JMS headers. (It would provide more immediately useful information than Exchange ID.) I'm not sure how to add the property, though, since it's not one of the five properties supported out-of-the-box[1]. A

workaround for CAMEL-4264

Hi Camel folks, I'm currently struggling from CAMEL4264[1] in route that looks like: JMS -> log -> stream resequencer -> log -> processor Unfortunately, the exception is thrown between the 2nd log and processor, and caught and logged (at DEBUG level!) by the StreamResequencer. So the affected m

Re: never deliver out-of-order message with resequencer

On Wed, Aug 10, 2011 at 10:25 AM, Claus Ibsen wrote: > In fact we may add support directly on the resequencer as well to > filter out out of sequence numbers in case it have send out a batch. > Fell free to create a JIRA ticket. And if possible working on a patch > with unit test. Done, see

Re: never deliver out-of-order message with resequencer

On Wed, Aug 10, 2011 at 7:42 AM, Claus Ibsen wrote: > On Tue, Aug 9, 2011 at 5:05 PM, David Tombs wrote: >> Hi all, >> >> I am using the resequencer EIP in a situation where it would be better >> never to pass on a message at all than to process it out-of-order. The &g

never deliver out-of-order message with resequencer

Hi all, I am using the resequencer EIP in a situation where it would be better never to pass on a message at all than to process it out-of-order. The EIP, however, will deliver out-of-order messages if the timeout occurs before receiving an expected message. For example, we receive: 1, 2, 3, 4, 5

Re: Multiple Expressions in Spring XML

On Mon, Aug 8, 2011 at 10:06 AM, Claus Ibsen wrote: > On Mon, Aug 8, 2011 at 3:38 PM, David Tombs wrote: >> Hi all, >> >> Is it possible to use multiple Expressions in the Spring XML >> element? I'd like to do the equivalent of: >> >> resequence

Multiple Expressions in Spring XML

Hi all, Is it possible to use multiple Expressions in the Spring XML element? I'd like to do the equivalent of: resequence(header("mySeqNo"), header("MyCustomerRating")) in Spring XML, but I can't find a way to do that which fits the XML schema. Thanks in advance, David -- Wise men _still_ s

Re: DefaultEndpoint constructors

On Thu, Jan 13, 2011 at 1:03 AM, Claus Ibsen wrote: > The default ctr is used if you create the endpoints manually (without > using a component), for example in a spring xml file using the > style. Then its easier to avoid having to use the ugly > > > If you do that you are responsible for setti

Re: NotifyBuilder and MockEndpoint message count

On Fri, Jan 21, 2011 at 3:59 PM, David Tombs wrote: >>> Hello all, >>> >>> While using the great testing utilities that camel provides, I have >>> noticed that NotifyBuilder and MockEndpoint provide options for a >>> minimum message received count (ex

NotifyBuilder and MockEndpoint message count

Hello all, While using the great testing utilities that camel provides, I have noticed that NotifyBuilder and MockEndpoint provide options for a minimum message received count (expectedMinimumMessageCount) and an exact message received count (expectedMessageCount). However, as far as I can tell fr

DefaultEndpoint constructors

Hello all, I'm currently writing my own camel component right now. In all the example code I see, the constructor DefaultEndpoint(String endpointUri, Component component) is used. I tried using the constructor DefaultEndpoint() but then got some exceptions, so I'm assuming that DefaultEndpoint()

Re: Freeing objects returned by type converter

On Mon, Jan 10, 2011 at 5:03 AM, Willem Jiang wrote: > On 1/8/11 12:45 AM, David Tombs wrote: > > >> On Fri, Jan 7, 2011 at 10:39 AM, Claus Ibsen >> wrote: >> >> >> >>> On Fri, Jan 7, 2011 at 4:14 PM, David Tombs >>> wrote: >>&g

Re: Freeing objects returned by type converter

On Fri, Jan 7, 2011 at 10:39 AM, Claus Ibsen wrote: > On Fri, Jan 7, 2011 at 4:14 PM, David Tombs wrote: > > On 1/7/11, James Strachan wrote: > >> On 7 January 2011 14:51, David Tombs wrote: > >>> Hello all, > >>> > >>> I have recently

Re: Freeing objects returned by type converter

On 1/7/11, James Strachan wrote: > On 7 January 2011 14:51, David Tombs wrote: >> Hello all, >> >> I have recently started using camel and it's fantastic. Thanks for all >> your hard work, committers. > > Thanks! > >> One issue I came across is whe

Freeing objects returned by type converter

Hello all, I have recently started using camel and it's fantastic. Thanks for all your hard work, committers. One issue I came across is whether I should free or close objects returned by a type converter. For example, I have a class that reads some binary data from an InputStream so I wrote a cu