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 2010/09/03 15:42:42 UTC
[jira] Commented: (CAMEL-3092) We should make it clearer that
clientId and durableSubscriptionName are needed for a durable sub
[ https://issues.apache.org/activemq/browse/CAMEL-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61663#action_61663 ]
Claus Ibsen commented on CAMEL-3092:
------------------------------------
If {{clientId}} is not configured then an IllegalArgumentException is thrown on startup.
> We should make it clearer that clientId and durableSubscriptionName are needed for a durable sub
> ------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3092
> URL: https://issues.apache.org/activemq/browse/CAMEL-3092
> Project: Apache Camel
> Issue Type: Task
> Components: camel-jms
> Affects Versions: 2.4.0
> Reporter: Jonathan Anstey
> Assignee: Claus Ibsen
> Fix For: 2.5.0
>
>
> We currently have the subscriptionDurable option to force Camel to try and create a durable subscription. This gives a user the option of say only setting the durableSubscriptionName and trying to create a durable sub without a clientId. I think we should deprecate subscriptionDurable or at least log a WARN that both clientId and durableSubscriptionName are needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.