camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dewitte Pierre-Alban <>
Subject Camel MongoDB : Remove option invokeGetLastError
Date Sun, 29 Mar 2015 19:11:16 GMT

I currently trie to remove all deprecated use of MongoDB Java driver to
ease the migration from 2.13 to 3.0 when it will be realease.

Since version 2.13 of Java Driver, lt of method in WriteResult object are
deprecated .
As explain, the MongoClient should relie on the write concern and not use
the getLastError or getCachedLastError. If my french is good
the invokeGetLastError option of the component is also useless and we
should invite people to use the right write concern.

How do you manage such a case in Camel ? Is it possible to depreciate a
attribute to remove it in a further version ? Do you remove it immediatly ?
Do we keep it but with no effect ?

Thanks for you replie.

Pierre-Alban DEWITTE

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message