Could you please direct me to a an easy to follow example / component to copy
from to develop a custom transactional consumer component.
I have some experience with developing components (producers mainly), so
what I am after is a guide how to approach transactional controls on top of
it - essenti
Yep, I saw that.
Thanks for the time fix.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-salesforce-component-add-support-for-lookup-field-tp5784605p5784945.html
Sent from the Camel Development mailing list archive at Nabble.com.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1063
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
GitHub user snesneros opened a pull request:
https://github.com/apache/camel/pull/1070
Update hbase.adoc
There is a typo in the documentation for the hbase compontent.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/snesneros/came
Hello,
In https://issues.apache.org/jira/browse/CAMEL-9880 Stephan proposes an
improvement for the attachment concept in Camel.
He introduces headers for attachments. Currently an attachment is
represented in Camel by a DataHandler; in the Camel
Message you have methods like
DataHandler getAt
Github user nicolaferraro closed the pull request at:
https://github.com/apache/camel/pull/1069
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user borcsokj closed the pull request at:
https://github.com/apache/camel/pull/1068
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
