[
https://issues.apache.org/jira/browse/CAMEL-10554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15719691#comment-15719691
]
Terrien Jean-Yves commented on CAMEL-10554:
-------------------------------------------
In the camel component configuration an option is outputType which is
implemented as a MongoDbOutputType enumeration
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 classes.
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.
A+JYT
> camel-mongodb evolution to driver 3
> -----------------------------------
>
> Key: CAMEL-10554
> URL: https://issues.apache.org/jira/browse/CAMEL-10554
> 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 component.
> I'm working on the evolution of this component to use the new classes of
> version 3, like "Document".
> I've created à patch (no completed)
> A+JYT
> Ps: how I can post the patch ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
