Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
Today both the operationName and topicName are marked as optional - which makes the logic to parse the uri complex.
A rule in Camel is that only one path parameter can be optional.
It would be better to make operationName mandatory and add an operation for the consumer (what would be a good name, listen, consume, onMessage?), so you would do
from("salesforce:listen:cheese")
And in the uri for the producer uses the operationName already, where topicName is not in use.
to("salesforce:updateSObject")