Hi Dominic,
Good catch. I have just created an issue to trac that support for
your use case has been added.
see issue: https://issues.apache.org/activemq/browse/CAMEL-129
The JMS endpoint now supports a a preserveMessageQos={boolean} option.
This option is used by the endpoint producer when sending a message to
JMS to determine if it should use the QoS options that are in the
message that it is given when sending.
example usage:
from("activemq:queue:p1").to("activemq:queue:p2?preserveMessageQos=true");
If you want try it out.. either rebuild the camel trunk source or wait
for a nightly snapshot.
Regards,,
Hiram
On 8/29/07, DominicTulley <[EMAIL PROTECTED]> wrote:
>
> Hi. It looks to me like the JMSExpiration header is not surviving routing
> through Camel.
> Using the ProducerTool and ConsumerTool examples that come with ActiveMQ and
> setting a TimeToLive puts a value in the JMSExpiration header, but by the
> time it's been routed to another queue the value is 0.
>
> I know some work has been done recently to improve the set of headers being
> maintained during routing but as far as I can tell this one still doesn't.
> I've tried the 1.1 release and I think (!) I got the latest source from svn
> (but I'm no expert with that).
>
> Thanks,
>
> -Dominic
> --
> View this message in context:
> http://www.nabble.com/JMSExpiration-not-being-maintained-by-routing--tf4346887s22882.html#a12384229
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
