[
https://issues.apache.org/jira/browse/CAMEL-10849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878091#comment-15878091
]
Zoran Regvart commented on CAMEL-10849:
---------------------------------------
[~lb] I've committed a fix for this. The CometD client is still tied to the
component, I think this makes sense as the number of clients connected to
Salesforce is limited (per edition you run). I've change the way the replay
support is configured and those properties (`defaultReplayId` and
`initialReplayIdMap`) set on endpoint configuration should be taken into
account, and preferred over the configuration on the component.
With the CometD client tied to component, this means that you cannot configure
per-endpoint HTTP client, I don't see it as a great disadvantage, but it could
be addressed by creating a new CometD client if the HTTP client on the
component and on the endpoint differ.
Can you give it a spin and close this if it's now OK for you?
> 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)
