[
https://issues.apache.org/activemq/browse/CAMEL-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-469:
------------------------------
Affects Version/s: 1.3.0
(was: 1.4.0)
> Allow replyTo destination to receive its own persistentDelivery QoS
> -------------------------------------------------------------------
>
> Key: CAMEL-469
> URL: https://issues.apache.org/activemq/browse/CAMEL-469
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.3.0
> Reporter: Marat Bedretdinov
> Fix For: 1.4.0
>
> Attachments: camel-jms.2008.04.16-20.45.patch
>
>
> IBM MQ provides dynamic with with persistent and non-persistent delivery mode
> QoS. if a dynamic queue with non-persistent delivery model is used to send a
> reply the broker will reject any messages sent with persistent delivery mode.
> The patch allows jms component to set delivery mode for producer for replyTo
> destination independently of producer for request destination.
> Generally speaking it would make sense to allow independent JmsConfiguration
> instances for JmsProducer and JmsConsumer that inherit their values off
> configuration that belongs to JmsEndpoint . This way producer's and
> consumer's QoS can differ and be independently configured.
> This is a cumulative patch with work done for
> https://issues.apache.org/activemq/browse/CAMEL-467
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
