camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heath Kesler (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3781) Add option to disable expiration on JMS component
Date Tue, 05 Apr 2011 13:49:05 GMT


Heath Kesler commented on CAMEL-3781:

@Hadrian - Does Bryan's response make sense?  I do agree with you, that new options complicate
URIs, documentation, etc. and I would prefer to avoid that when possible also.  I do not see
a way of implementing Bryan's suggested improvement without one, but I am open to suggestions.
 I did make the default function the way Claus suggested in the link, so current implementations
would not see a change.

@Bryan - did you look at the patch?  Does it solve your request the way you have defined it?
 Checkout the test, that should layout the functionality pretty well and give you an idea
of what was implemented.  

> Add option to disable expiration on JMS component
> -------------------------------------------------
>                 Key: CAMEL-3781
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jms
>    Affects Versions: 2.6.0
>         Environment: Java 1.6.0_24, Mac OS X 10.6.6
>            Reporter: Bryan Keller
>            Priority: Minor
>             Fix For: 2.8.0
>         Attachments: patch-3781.diff
> It would be nice to add an option to the JMS component to disable the use of message
expirations for InOut exchanges. If a client and server have clocks that are out-of-sync,
using message expiration can cause problems. More details can be found here:

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message