[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880926#comment-15880926
]
Sune Keller commented on CAMEL-10849:
-------------------------------------
[~lb] I agree completely. So at the endpoint level, there would only be a
single replayId URI parameter, {{replayId}}, which would override any default
or initial replay IDs. This would only be useful if you're not actually using
the replay functionality, or if you always want to play back the past 24 hours
by setting the value to {{-2}}. Am I missing any other obvious use cases?
> Salesforce: subscription channel created per component
> ------------------------------------------------------
>
> Key: CAMEL-10849
> URL: https://issues.apache.org/jira/browse/CAMEL-10849
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
> Reporter: Luca Burgazzoli
> Assignee: Zoran Regvart
> Fix For: 2.19.0
>
>
> If I creates two salesforce consumers, I can't set different options per
> channel as the client is configured on component level so i.e. you can't set
> a per channel replay id as only the first one is taken into account:
> {code:java}
> from('salesforce:comments-1?updateTopic=true&sObjectQuery=SELECT Id,
> CommentId__c FROM Comment_Event__c')
>
> .to("log:salesforce-comments?level=INFO&showHeaders=false&multiline=false")
> from('salesforce:comments-2?updateTopic=true&sObjectQuery=SELECT Id FROM
> Case')
>
> .to("log:salesforce-cases?level=INFO&showHeaders=false&multiline=false")
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
