[
https://issues.apache.org/jira/browse/CAMEL-22033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948578#comment-17948578
]
Jesse Sightler commented on CAMEL-22033:
----------------------------------------
That would be fine with me. It would be good to also get the rpc-id, as they
have been asking for that as well today. Having both of those in a header would
eliminate the need to access the ConsumerEvent.
> camel-salesforce - For the Pub/Sub API, add the original ConsumerEvent as an
> exchange property
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-22033
> URL: https://issues.apache.org/jira/browse/CAMEL-22033
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
> Reporter: Jesse Sightler
> Priority: Minor
>
> Each salesforce event is shipped with a unique identifier in the id field.
> Unfortunately, this id is not accessible within the camel API.
> Pub Sub API gets replay id, but not other identifying fields:
> [https://github.com/apache/camel/blob/camel-4.4.1/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/client/PubSubApiClient.java]
> Ideally, either the message id, or the entire consumer event could be placed
> into an exchange property for use by consuming camel routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
