camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4878) Create a Camel component for MongoDB
Date Thu, 16 Feb 2012 15:53:00 GMT


Claus Ibsen commented on CAMEL-4878:

Yeah if you do compensation logic in the component, then you need to handle that yourself.
If for example mongodb has some natural support for compensation or retry etc.

Normally for the producer you would just throw the exception, and then the routing engine
will take care of it.

And for the consumer, you would normally have to do a try .. catch where you process the created
exchange. And in case of an exception, then that is consumer specific. There is a default
exception handler that just logs the exception at WARN level.
> Create a Camel component for MongoDB
> ------------------------------------
>                 Key: CAMEL-4878
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>    Affects Versions: 2.9.0
>            Reporter: Raul Kripalani
>            Assignee: Raul Kripalani
>             Fix For: 2.10.0
>         Attachments:
> As you know, NoSQL technology is evolving at an impressive rate and the adoption is increasing
> One of the most popular databases in this area is definitely MongoDB, a highly-performant,
scalable, schema-less database which stores information as flexible documents (meaning JSON
payloads, not Office, PDF, etc. or binary formats). 
> Unfortunately, the only support I have found for MongoDB is an Idempotent Repository
implementation backed up by Mongo ( 
> My proposal is to create a Camel component to support CRUD operations on MongoDB databases.
In most cases it will be a producer (create, read, update, delete), but it could also act
like a consumer performing scheduled polls (read-only) to fetch information from a collection.
MapReduce support can also be provided for complex queries. 
> When it comes to licensing there should be no restriction since the Java driver is licensed
under the Apache license ( 
> For more info see

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message