You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/07/02 07:18:08 UTC
[jira] Created: (CAMEL-1783) camel-jms - allow a header like
JMSDestination to override the destination to send to
camel-jms - allow a header like JMSDestination to override the destination to send to
-------------------------------------------------------------------------------------
Key: CAMEL-1783
URL: https://issues.apache.org/activemq/browse/CAMEL-1783
Project: Apache Camel
Issue Type: Improvement
Components: camel-jms
Affects Versions: 2.0-M2, 1.6.1
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 1.6.2, 2.0.0
We *cannot* use JMSDestination as it would not work when you do a route from(jms A) to (jms B) as it will go into round about as when received from jms A the header will contain JMSDestination = queue:A and thus Camel will send it back to itself.
So we should a different name
{{CamelJmsDestination}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1783) camel-jms - allow a header like
JMSDestination to override the destination to send to
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1783.
--------------------------------
Resolution: Fixed
1.x: 790547.
> camel-jms - allow a header like JMSDestination to override the destination to send to
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-1783
> URL: https://issues.apache.org/activemq/browse/CAMEL-1783
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.6.1, 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.6.2, 2.0.0
>
>
> We *cannot* use JMSDestination as it would not work when you do a route from(jms A) to (jms B) as it will go into round about as when received from jms A the header will contain JMSDestination = queue:A and thus Camel will send it back to itself.
> So we should a different name
> {{CamelJmsDestination}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1783) camel-jms - allow a header like
JMSDestination to override the destination to send to
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52627#action_52627 ]
Claus Ibsen commented on CAMEL-1783:
------------------------------------
The idea is to reuse the same endpoint but being able to send it to a destination of choice. This will reduce the number of endpoints needed in case you send JMS message to thousands of different JMS queues.
> camel-jms - allow a header like JMSDestination to override the destination to send to
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-1783
> URL: https://issues.apache.org/activemq/browse/CAMEL-1783
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.6.1, 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.6.2, 2.0.0
>
>
> We *cannot* use JMSDestination as it would not work when you do a route from(jms A) to (jms B) as it will go into round about as when received from jms A the header will contain JMSDestination = queue:A and thus Camel will send it back to itself.
> So we should a different name
> {{CamelJmsDestination}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1783) camel-jms - allow a header like
JMSDestination to override the destination to send to
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52629#action_52629 ]
Claus Ibsen commented on CAMEL-1783:
------------------------------------
trunk: 790476.
> camel-jms - allow a header like JMSDestination to override the destination to send to
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-1783
> URL: https://issues.apache.org/activemq/browse/CAMEL-1783
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.6.1, 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.6.2, 2.0.0
>
>
> We *cannot* use JMSDestination as it would not work when you do a route from(jms A) to (jms B) as it will go into round about as when received from jms A the header will contain JMSDestination = queue:A and thus Camel will send it back to itself.
> So we should a different name
> {{CamelJmsDestination}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1783) camel-jms - allow a header like
JMSDestination to override the destination to send to
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52628#action_52628 ]
Claus Ibsen commented on CAMEL-1783:
------------------------------------
Added two headers
- {{CamelJmsDestination}}
- {{CamelJmsDestinationName}}
Then you can reuse the same endpoint but send to a different JMS queue.
> camel-jms - allow a header like JMSDestination to override the destination to send to
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-1783
> URL: https://issues.apache.org/activemq/browse/CAMEL-1783
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.6.1, 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.6.2, 2.0.0
>
>
> We *cannot* use JMSDestination as it would not work when you do a route from(jms A) to (jms B) as it will go into round about as when received from jms A the header will contain JMSDestination = queue:A and thus Camel will send it back to itself.
> So we should a different name
> {{CamelJmsDestination}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1783) camel-jms - allow a header like
JMSDestination to override the destination to send to
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-1783:
-----------------------------------
Fix Version/s: (was: 2.0.0)
2.0-M3
> camel-jms - allow a header like JMSDestination to override the destination to send to
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-1783
> URL: https://issues.apache.org/activemq/browse/CAMEL-1783
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 1.6.1, 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.6.2, 2.0-M3
>
>
> We *cannot* use JMSDestination as it would not work when you do a route from(jms A) to (jms B) as it will go into round about as when received from jms A the header will contain JMSDestination = queue:A and thus Camel will send it back to itself.
> So we should a different name
> {{CamelJmsDestination}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.