You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are using kamelets/salesforce-update-sink.kamelet.yaml in openshift and getting this error while calling the salesforce endpoint using TOD uri in kamelets/salesforce-update-sink.kamelet.yaml to update salesforce sObject
org.apache.camel.NoSuchEndpointException: No endpoint could be found for: local-salesforce-2://updateSObject?rawPayload=true&sObjectId=aH17A00000006GZSAY&sObjectName=KameletSink__c, please check your classpath contains the needed Camel component jar
We are running the attached following kafka-sf-binding.yaml in openshift Kafka-sf-binding.txt
and using kamelets/salesforce-update-sink.kamelet.yaml to update sObject in salesforce
while publishing the following JSON in Kafka :-
On further investigation of logs, i saw TOD is appending the "-2" suffix to the bean name reference making it localhost-salesforce-2 in uri whereas bean name in the YAML is localhost-salesforce
we are using kamelets/salesforce-update-sink.kamelet.yaml in openshift and getting this error while calling the salesforce endpoint using TOD uri in kamelets/salesforce-update-sink.kamelet.yaml to update salesforce sObject
org.apache.camel.NoSuchEndpointException: No endpoint could be found for: local-salesforce-2://updateSObject?rawPayload=true&sObjectId=aH17A00000006GZSAY&sObjectName=KameletSink__c, please check your classpath contains the needed Camel component jar
We are running the attached following kafka-sf-binding.yaml in openshift
Kafka-sf-binding.txt
and using kamelets/salesforce-update-sink.kamelet.yaml to update sObject in salesforce
while publishing the following JSON in Kafka :-
getting this complete exception log
kafka-source-updat-sink-binding-7d5f6575f6-vj2kh-integration (1).log
The text was updated successfully, but these errors were encountered: