camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Terrien Jean-Yves (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10554) camel-mongodb evolution to driver 3
Date Sun, 04 Dec 2016 10:08:58 GMT


Terrien Jean-Yves commented on CAMEL-10554:

In the camel component configuration an option is outputType which is implemented as a MongoDbOutputType
The values ​​are DBObjectList, DBObject, DBCursor which matches in the new API to List<Document>,
Document, MongoIterable 

I do not know what to do. This configuration is purely camel 
I can keep the enumeration values ​​and use the new classes 
Or define three new values (DocumentList, Document, MongoIterable) ​​and using the new

In the first case the values ​​of the option does not have a name to refer to the mongo
API but remains compatible with the previous versions of camel-mongodb. 
In the second the values ​​correspond to the mongo API but are no longer compatible with
the previous versions. 


> camel-mongodb evolution to driver 3
> -----------------------------------
>                 Key: CAMEL-10554
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.19.0
>            Reporter: Terrien Jean-Yves
>            Assignee: Andrea Cosentino
>            Priority: Minor
>         Attachments: mongo3.patch
> Hi, 
> The mongodb driver has changed in its foundation. 
> It is recommended not to use many classes of the verion 2 still present in the driver.

> This is the case with DBObject, which is the basis for the configuration of the camel
> I'm working on the evolution of this component to use the new classes of version 3, like
> I've created à patch (no completed)
> Ps: how I can post the patch ?

This message was sent by Atlassian JIRA

View raw message