You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2007/08/29 18:02:23 UTC
[jira] Created: (CAMEL-129) Support preserving the original message
QoS options when a message gets re-sent to a JMS destination
Support preserving the original message QoS options when a message gets re-sent to a JMS destination
-----------------------------------------------------------------------------------------------------
Key: CAMEL-129
URL: https://issues.apache.org/activemq/browse/CAMEL-129
Project: Apache Camel
Issue Type: New Feature
Components: camel-jms
Affects Versions: 1.0.0
Reporter: Hiram Chirino
Assignee: Hiram Chirino
Fix For: 1.2.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-129) Support preserving the original message
QoS options when a message gets re-sent to a JMS destination
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated 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:
{code}
from("activemq:queue:p1").to("activemq:queue:p2?preserveMessageQos=true");
{code}
> Support preserving the original message QoS options when a message gets re-sent to a JMS destination
> -----------------------------------------------------------------------------------------------------
>
> Key: CAMEL-129
> URL: https://issues.apache.org/activemq/browse/CAMEL-129
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-jms
> Affects Versions: 1.0.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 1.2.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-129) Support preserving the original
message QoS options when a message gets re-sent to a JMS destination
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40045 ]
Hiram Chirino commented on CAMEL-129:
-------------------------------------
The lack of support for doing this was first noticed on this thread:
http://www.nabble.com/JMSExpiration-not-being-maintained-by-routing--tf4346887s22882.html
> Support preserving the original message QoS options when a message gets re-sent to a JMS destination
> -----------------------------------------------------------------------------------------------------
>
> Key: CAMEL-129
> URL: https://issues.apache.org/activemq/browse/CAMEL-129
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-jms
> Affects Versions: 1.0.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 1.2.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-129) Support preserving the original
message QoS options when a message gets re-sent to a JMS destination
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved CAMEL-129.
---------------------------------
Resolution: Fixed
fixed in trunk in rev 570851
> Support preserving the original message QoS options when a message gets re-sent to a JMS destination
> -----------------------------------------------------------------------------------------------------
>
> Key: CAMEL-129
> URL: https://issues.apache.org/activemq/browse/CAMEL-129
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-jms
> Affects Versions: 1.0.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 1.2.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.