- camel-neo4j - To integrate with the graph database neo4j
- camel-couchdb - To integrate with the Apache CouchDB
- camel-elastichsearch - To interface with an ElastichSearch Server
- camel-cmis - To integrate with CMIS compliant content repository
- camel-sjms - JMS component with pure JMS API (no 3rd party like spring-jms)
All five components started by members of the community, and not by people from the Camel team. For example the camel-neo4j, and camel-couchdb components is kindly donated to ASF by Stephen Samuel. Bilgin Ibryam contributed the camel-cmis component. And Cedric Vidal donated the camel-elastichsearch component. And lastly Scott Sullivan donated the camel-sjms component.
Since then Scott and Bilgin has been invited into the Camel team, and both are Camel committers today. Scott will continue improved and work on camel-sjms. At this time we are looking for people who wanna give the current code a test-spin. It does take some time to harden this component to become as stable and good as the current camel-jms component. We anticipate this is ongoing work over the next couple of Camel releases.
You can click on the links in the bulleted list to get to the Camel documentation for each of these components, which has some sample code as well.
Also expect much improved CDI support from Camel in 2.11.
The current in-progress release notes of changes in Camel 2.11 can be seen here.
Thanks a lot to the very active Camel community and for people taking up the time to write components that benefit all of us. Keep up the great work.
And in case you did not know, Apache Camel comes with a lot of components out of the box. The screenshot below is a directory listing from my laptop with the trunk code.
|Camel Components Galore|
PS: There is 133 components.