Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 63FBB186DD for ; Wed, 14 Oct 2015 20:19:49 +0000 (UTC) Received: (qmail 15123 invoked by uid 500); 14 Oct 2015 20:19:36 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 15072 invoked by uid 500); 14 Oct 2015 20:19:36 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 15063 invoked by uid 99); 14 Oct 2015 20:19:36 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Oct 2015 20:19:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E6AE6C0257 for ; Wed, 14 Oct 2015 20:19:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.241 X-Spam-Level: ** X-Spam-Status: No, score=2.241 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_HUGEIMGSRC=0.2, KAM_LAZY_DOMAIN_SECURITY=1, KAM_LOTSOFHASH=0.25, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 3yXEnpHN4srK for ; Wed, 14 Oct 2015 20:19:17 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTP id 630EC2326E for ; Wed, 14 Oct 2015 20:19:17 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D9661E047F for ; Wed, 14 Oct 2015 20:19:16 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 5DC763A09FC for ; Wed, 14 Oct 2015 20:19:16 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r968937 - in /websites/production/camel/content: 2015/10/14/ 2015/10/14/welcome-jean-baptiste-onofr-as-camel-pmc-member.html 2015/10/14/welcome-sergey-beryozkin-as-camel-committer.html cache/main.pageCache index.html mongodb.html news.html Date: Wed, 14 Oct 2015 20:19:16 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20151014201916.5DC763A09FC@svn01-us-west.apache.org> Author: buildbot Date: Wed Oct 14 20:19:15 2015 New Revision: 968937 Log: Production update by buildbot for camel Added: websites/production/camel/content/2015/10/14/ websites/production/camel/content/2015/10/14/welcome-jean-baptiste-onofr-as-camel-pmc-member.html websites/production/camel/content/2015/10/14/welcome-sergey-beryozkin-as-camel-committer.html Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/index.html websites/production/camel/content/mongodb.html websites/production/camel/content/news.html Added: websites/production/camel/content/2015/10/14/welcome-jean-baptiste-onofr-as-camel-pmc-member.html ============================================================================== --- websites/production/camel/content/2015/10/14/welcome-jean-baptiste-onofr-as-camel-pmc-member.html (added) +++ websites/production/camel/content/2015/10/14/welcome-jean-baptiste-onofr-as-camel-pmc-member.html Wed Oct 14 20:19:15 2015 @@ -0,0 +1,147 @@ + + + + + + + + + + + + + + + + + + + Apache Camel: Welcome Jean-Baptiste Onofré as Camel PMC member + + + +
+
+
+
+
+
+
+
+
+
+
+ + + +
+ + + + +
+ + + + + + + + +
+

The Apache Camel user community is growing constantly. It is also very rewarding to see that most of the contributors who became committers continue to stay involved. Therefore, in recognition of the continued contribution, the Apache Camel PMC invited Jean-Baptiste Onofré to join the PMC, be even more involved and take a greater responsibility in shaping the future of the Camel project. I'm sure most of you already know JB. He is an Apache member and in the PMC of Apache Ace, Archiva, Aries, Falcon, Incubator, Karaf, Lens, Servicemix & Syncope. Beside this, he is also a committer in Apache ActiveMQ and JClouds.

 

Many thanks for your past contributions and we look forward to the same commitment in the future.

 

Christian Müller,

VP, Apache Camel

+ 		+
+
+ + + +
+
+
+ + +
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+© 2004-2015 The Apache Software Foundation. +
+Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners. +
+Graphic Design By Hiram +
+ + + + + + + + Added: websites/production/camel/content/2015/10/14/welcome-sergey-beryozkin-as-camel-committer.html ============================================================================== --- websites/production/camel/content/2015/10/14/welcome-sergey-beryozkin-as-camel-committer.html (added) +++ websites/production/camel/content/2015/10/14/welcome-sergey-beryozkin-as-camel-committer.html Wed Oct 14 20:19:15 2015 @@ -0,0 +1,147 @@ + + + + + + + + + + + + + + + + + + + Apache Camel: Welcome Sergey Beryozkin as Camel committer + + + +
+
+
+
+
+
+
+
+
+
+
+ + + +
+ + + + +
+ + + + + + + + +
+

The Apache Camel PMC is pleased to introduce Sergey Beryozkin as a new committer. We are very happy with the sustained growth of the project and look forward to continued contributions from the community and adding to the ranks of Camel Riders. Sergey was involved with Camel for well over long time now, especially with Camel CXF. He contributed to the code and got involved with the community on the mailing lists.

 

On behalf of the Camel PMC, welcome aboard and we expect more great things coming from you!

 

Christian Müller,

VP, Apache Camel

+ 		+
+
+ + + +
+
+
+ + +
+
+
+
+
+
+
+
+
+ +
+
+
+
+
+
+© 2004-2015 The Apache Software Foundation. +
+Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners. +
+Graphic Design By Hiram +
+ + + + + + + + Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/index.html ============================================================================== --- websites/production/camel/content/index.html (original) +++ websites/production/camel/content/index.html Wed Oct 14 20:19:15 2015 @@ -99,17 +99,17 @@ There's a great discussion about Camel a

- - + + - Apache Camel 2.16.0 Released -
Daniel Kulp posted on Oct 09, 2015
+ Welcome Sergey Beryozkin as Camel committer +
Christian Mueller posted on Oct 14, 2015
-

The Camel community announces the immediate availability of the new major release Camel 2.16.0. This release contains a total of 600+ fixes applied in the past 6 months by the community on the Camel master branch.  

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes.   

Many thanks to all who made this release possible.   

On behalf of the Camel PMC,   

Dan

+

The Apache Camel PMC is pleased to introduce Sergey Beryozkin as a new committer. We are very happy with the sustained growth of the project and look forward to continued contributions from the community and adding to the ranks of Camel Riders. Sergey was involved with Camel for well over long time now, especially with Camel CXF. He contributed to the code and got involved with the community on the mailing lists.

 

On behalf of the Camel PMC, welcome aboard and we expect more great things coming from you!

 

Christian Müller,

VP, Apache Camel

@@ -123,13 +123,13 @@ There's a great discussion about Camel a - We welcome two new PMC members -
Christian Mueller posted on Sep 25, 2015
+ Welcome Jean-Baptiste Onofré as Camel PMC member +
Christian Mueller posted on Oct 14, 2015
-

The Apache Camel user community is growing constantly with increased adoption. We are grateful to our users who decide to give something back in the form of reporting bugs, providing patches and contributing to the documentation. The project would not be what it is without the community contributions. We want to see more of you helping out and the most active join us as committers. It is also very rewarding to see that most of the contributors who became committers continue to stay involved. Therefore, in recognition of their continued contribution, the Apache Camel PMC invited recently Aki Yoshida and Andrea Cosentino to join the PMC, be even more involved and take a greater responsibility in shaping the future of the Camel project. We welcome both as new Apache Camel PMC members. Many thanks for your past contributions and we look forward to the same commitment in the future.

On behalf of the Camel PMC, welcome aboard and we expect more great things coming from yo u!

Christian Müller,

 

VP, Apache Camel

+

The Apache Camel user community is growing constantly. It is also very rewarding to see that most of the contributors who became committers continue to stay involved. Therefore, in recognition of the continued contribution, the Apache Camel PMC invited Jean-Baptiste Onofré to join the PMC, be even more involved and take a greater responsibility in shaping the future of the Camel project. I'm sure most of you already know JB. He is an Apache member and in the PMC of Apache Ace, Archiva, Aries, Falcon, Incubator, Karaf, Lens, Servicemix & Syncope. Beside this, he is also a committer in Apache ActiveMQ and JClouds.

 

Many thanks for your past contributions and we look forward to the same commitment in the future.

 

Christian Müller,

VP, Apache Camel

@@ -143,13 +143,13 @@ There's a great discussion about Camel a - Apache Camel 2.15.3 -
Daniel Kulp posted on Aug 21, 2015
+ Apache Camel 2.16.0 Released +
Daniel Kulp posted on Oct 09, 2015
-

The Camel community announces the immediate availability of the new patch release Camel 2.15.3. This release contains over 100 fixes applied in the past few weeks by the community on the Camel 2.15.x maintenance branch.

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes .

Many thanks to all who made this release possible.

On behalf of the Camel PMC,

Dan

+

The Camel community announces the immediate availability of the new major release Camel 2.16.0. This release contains a total of 600+ fixes applied in the past 6 months by the community on the Camel master branch.  

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes.   

Many thanks to all who made this release possible.   

On behalf of the Camel PMC,   

Dan

@@ -159,17 +159,17 @@ There's a great discussion about Camel a
- - + + - Release Apache Camel 2.14.3 -
willem jiang posted on Jun 02, 2015
+ We welcome two new PMC members +
Christian Mueller posted on Sep 25, 2015
-

The Camel community announces the immediate availability of the new patch release Camel 2.14.3. This release contains a total of 80 fixes applied in the past few weeks by the community on the Camel 2.14.x maintenance branch. 

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes. 

Many thanks to all who made this release possible. 

On behalf of the Camel PMC, 

Willem Jia ng

+

The Apache Camel user community is growing constantly with increased adoption. We are grateful to our users who decide to give something back in the form of reporting bugs, providing patches and contributing to the documentation. The project would not be what it is without the community contributions. We want to see more of you helping out and the most active join us as committers. It is also very rewarding to see that most of the contributors who became committers continue to stay involved. Therefore, in recognition of their continued contribution, the Apache Camel PMC invited recently Aki Yoshida and Andrea Cosentino to join the PMC, be even more involved and take a greater responsibility in shaping the future of the Camel project. We welcome both as new Apache Camel PMC members. Many thanks for your past contributions and we look forward to the same commitment in the future.

On behalf of the Camel PMC, welcome aboard and we expect more great things coming from yo u!

Christian Müller,

 

VP, Apache Camel

@@ -179,17 +179,17 @@ There's a great discussion about Camel a
- - + + - Apache Camel 2.15.2 Released -
willem jiang posted on May 05, 2015
+ Apache Camel 2.15.3 +
Daniel Kulp posted on Aug 21, 2015
-

The Camel community announces the immediate availability of the new patch release Camel 2.15.2. This release contains a total of 71 fixes applied in the past few weeks by the community on the Camel 2.15.x maintenance branch.

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes.

Many thanks to all who made this release possible.

On behalf of the Camel PMC,

Willem

+

The Camel community announces the immediate availability of the new patch release Camel 2.15.3. This release contains over 100 fixes applied in the past few weeks by the community on the Camel 2.15.x maintenance branch.

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes .

Many thanks to all who made this release possible.

On behalf of the Camel PMC,

Dan

@@ -199,17 +199,17 @@ There's a great discussion about Camel a
- - + + - Welcome Andrea Cosentino as the newest Camel Rider -
Christian Mueller posted on Apr 23, 2015
+ Release Apache Camel 2.14.3 +
willem jiang posted on Jun 02, 2015
-

Yesterday, the Camel PMC voted another one of the very active and talented contributors to become a committer.

Andrea Cosentino is actively involved with Apache Camel since months contributing code and helping other users. Andrea contributed many patches / pull requests for helping to maintain the Camel components and ensure they are using newer releases of the dependency JARs. He is also taking on OSGi and help upgrade and maintain the karaf features as well. He is also working on a cassandra Camel component at GitHub, porting this good stuff back.

On behalf of the Camel PMC, welcome aboard Andrea and keep up the great work!

Christian

+

The Camel community announces the immediate availability of the new patch release Camel 2.14.3. This release contains a total of 80 fixes applied in the past few weeks by the community on the Camel 2.14.x maintenance branch. 

The artifacts are published and ready for you to download either from the Apache mirrors or from the Central Maven repository. For more details please take a look at the release notes. 

Many thanks to all who made this release possible. 

On behalf of the Camel PMC, 

Willem Jia ng

Modified: websites/production/camel/content/mongodb.html ============================================================================== --- websites/production/camel/content/mongodb.html (original) +++ websites/production/camel/content/mongodb.html Wed Oct 14 20:19:15 2015 @@ -96,7 +96,7 @@

URI format

-

Endpoint options

MongoDB endpoints support the following options, depending on whether they are acting like a Producer or as a Consumer (options vary based on the consumer type too).

 

Name

Default Value

Description

Producer

Tailable Cursor Consumer

database

none

Required. The name of the database to which this endpoint will be bound. All operations will be executed against this database unless dynamicity is enabled and the CamelMongoDbDatabase header is set.

(tick)

(tick)

collection

none

Required (Except for getDbStats and command operations). The name of the collection (within the specified database) to which this endpoint will be bound. All operations will be executed against this database unless dynamicity is enabled and the CamelMongoDbDatabase header is set.

(tick)

(tick)

collectionIndex

none

Available as of Camel 2.12: An optional single field index or compound index to create when inserting new collections.

(tick)

 

operation

none

Required for producers. Th e id of the operation this endpoint will execute. Pick from the following:

  • Query operations: findById, findOneByQuery, findAll, count
  • Write operations: insert, save, update
  • Delete operations: remove
  • Other operations: getDbStats, getColStats, aggregate, command

(tick)

 

createCollection

true

Determines whether the collection will be automatically created in the MongoDB database during endpoint initialisation if it doesn't exist already. If this option is false and the collection doesn't exist, an initialisation exception will be thrown.

(tick)

 

invokeGetLastError

false (behaviour may be inherited from connections WriteConcern)

Remove in camel 2.16

Instructs the MongoDB Java driver to invok e getLastError() after every call. Default behaviour in version 2.7.2 of the MongoDB Java driver is that only network errors will cause the operation to fail, because the actual operation is executed asynchronously in the MongoDB server without holding up the client - to increase performance. The client can obtain the real result of the operation by explicitly invoking getLastError() on the WriteResult object returned or by setting the appropriate WriteConcern. If the backend operation has not finished yet, the client will block until the result is available. Setting this option to true will make the endpoint behave synchronously and return an Exception if the underlying operation failed.

WriteConcern should be preferred to detect if write occurs without errors. MongoDB strongly discourage to use this method as it is not reliable.

(tick)

 

writeConcern

none (driver's default)

Set a WriteConcern on the operation out of MongoDB's parameterised values. See WriteConcern.valueOf(String).

(tick)

 

writeConcernRef

none

Sets a custom WriteConcern that exists in the Registry. Specify the bean name.

(tick)

 

readPreference

none

Availab le as of Camel 2.12.4, 2.13.1 and 2.14.0: Sets a ReadPreference on the connection. Accepted values are those supported by the ReadPreference#valueOf() public API. Currently as of MongoDB-Java-Driver version 2.12.0 the supported values are: primary, primaryPreferred, secondary, secondaryPreferred and nearest. See also the documentation for more details about this option.

(tick)

 

dynamicity

false

If set to true, the endpoint will inspect the CamelMongoDbDatabase and CamelMongoDbCollection headers of the incoming message, and if any of them exists, the target collection and/or database will be overridden for that particular operation. Set to false by default to avoid triggering the lookup on every Exchange if the feature is not desired.

(tick)

 

writeResultAsHeader

false

Available as of Camel 2.10.3 and 2.11: In write operations (save, update, insert, etc.), instead of replacing the body with the WriteResult object returned by MongoDB, keep the input body untouched and place the WriteResult in the CamelMongoWriteResult header (constant MongoDbConstants.WRITERESULT).

(tick)

 

outputType
DBObjectList for findAll

DBObject for all other operations

Available as of Camel 2.16 : Convert the output of the producer to the selected type : "DBObjectList", "DBObject" or "DBCursor" :

  • DBObjectList or DBCursor (may be useful to stream the output) applies to findAll.
  • DBObject applies to all other operations.
(tick) 

persistentTailTracking

false

Enables or disables persistent tail tracking for Tailable Cursor consumers. See below for more information.

 

(tick)

persistentId

none

Required if persistent tail tracking is enabled. The id of this persistent tail tracker, to separate its records from the rest on the tail-tracking collection.

 

(tick)

tailTrackingIncreasingField

none

Required if persistent tail tracking is enabled. Corre lation field in the incoming record which is of increasing nature and will be used to position the tailing cursor every time it is generated. The cursor will be (re)created with a query of type: tailTrackIncreasingField > lastValue (where lastValue is possibly recovered from persistent tail tracking). Can be of type Integer, Date, String, etc. NOTE: No support for dot notation at the current time, so the field should be at the top level of the document.

 

(tick)

cursorRegenerationDelay

1000ms

Establishes how long the endpoint will wait to regenerate the cursor after it has been killed by the MongoDB server (normal behaviour).

 

(tick)

tailTrackDb

same as endpoint's

Database on which the persistent tail tracker will store its runtime information.

 

(tick)

tailTrackCollection

camelTailTracking

Collection on which the persistent tail tracker will store its runtime information.

 

(tick)

tailTrackField

lastTrackingValue

Field in which the persistent tail tracker will store the last tracked value.

 

(tick)

Configuration of database in Spring XML

The following Spring XML creates a bean defining the connection to a MongoDB instance.

+

Endpoint options

MongoDB endpoints support the following options, depending on whether they are acting like a Producer or as a Consumer (options vary based on the consumer type too).

 

Name

Default Value

Description

Producer

Tailable Cursor Consumer

database

none

Required. The name of the database to which this endpoint will be bound. All operations will be executed against this database unless dynamicity is enabled and the CamelMongoDbDatabase header is set.

(tick)

(tick)

collection

none

Required (Except for getDbStats and command operations). The name of the collection (within the specified database) to which this endpoint will be bound. All operations will be executed against this database unless dynamicity is enabled and the CamelMongoDbDatabase header is set.

(tick)

(tick)

collectionIndex

none

Available as of Camel 2.12: An optional single field index or compound index to create when inserting new collections.

(tick)

 

operation

none

Required for producers. Th e id of the operation this endpoint will execute. Pick from the following:

  • Query operations: findById, findOneByQuery, findAll, count
  • Write operations: insert, save, update
  • Delete operations: remove
  • Other operations: getDbStats, getColStats, aggregate, command

(tick)

 

createCollection

true

Determines whether the collection will be automatically created in the MongoDB database during endpoint initialisation if it doesn't exist already. If this option is false and the collection doesn't exist, an initialisation exception will be thrown.

(tick)

 

invokeGetLastError

false (behaviour may be inherited from connections WriteConcern)

Remove in camel 2.16

Instructs the MongoDB Java driver to invok e getLastError() after every call. Default behaviour in version 2.7.2 of the MongoDB Java driver is that only network errors will cause the operation to fail, because the actual operation is executed asynchronously in the MongoDB server without holding up the client - to increase performance. The client can obtain the real result of the operation by explicitly invoking getLastError() on the WriteResult object returned or by setting the appropriate WriteConcern. If the backend operation has not finished yet, the client will block until the result is available. Setting this option to true will make the endpoint behave synchronously and return an Exception if the underlying operation failed.

WriteConcern should be preferred to detect if write occurs without errors. MongoDB strongly discourage to use this method as it is not reliable.

(tick)

 

writeConcern

none (driver's default)

Set a WriteConcern on the operation out of MongoDB's parameterised values. See WriteConcern.valueOf(String).

(tick)

 

writeConcernRef

none

Sets a custom WriteConcern that exists in the Registry. Specify the bean name.

(tick)

 

readPreference

none

Availab le as of Camel 2.12.4, 2.13.1 and 2.14.0: Sets a ReadPreference on the connection. Accepted values are those supported by the ReadPreference#valueOf() public API. Currently as of MongoDB-Java-Driver version 2.12.0 the supported values are: primary, primaryPreferred, secondary, secondaryPreferred and nearest. See also the documentation for more details about this option.

(tick)

 

dynamicity

false

If set to true, the endpoint will inspect the CamelMongoDbDatabase and CamelMongoDbCollection headers of the incoming message, and if any of them exists, the target collection and/or database will be overridden for that particular operation. Set to false by default to avoid triggering the lookup on every Exchange if the feature is not desired.

(tick)

 

writeResultAsHeader

false

Available as of Camel 2.10.3 and 2.11: In write operations (save, update, insert, etc.), instead of replacing the body with the WriteResult object returned by MongoDB, keep the input body untouched and place the WriteResult in the CamelMongoWriteResult header (constant MongoDbConstants.WRITERESULT).

(tick)

 

outputType

DBObjectList for findAll
DBObject for all other operations

Available as of Camel 2.16 : Convert the output of the producer to the selected type : "DBObjectList", "DBObject" or "DBCursor" :
DBObjectList or DBCursor (may be useful to stream the output) applies to findAll.
DBObject applies to all other operations.

(tick)

 

persistentTailTracking

false

Enables or disables persistent tail tracking for Tailable Cursor consumers. See below for more information.

 

(tick)

persistentId

none

Required if persistent tail tracking is enabled. The id of this persistent tail tracker, to separate its records from the rest on the tail-tr acking collection.

 

(tick)

tailTrackingIncreasingField

none

Required if persistent tail tracking is enabled. Correlation field in the incoming record which is of increasing nature and will be used to position the tailing cursor every time it is generated. The cursor will be (re)created with a query of type: tailTrackIncreasingField > lastValue (where lastValue is possibly recovered from persistent tail tracking). Can be of type Integer, Date, String, etc. NOTE: No support for dot notation at the current time, so the field should be at the top level of the document.

 

(tick)

cursorRegenerationDelay

1000ms

Establishes how long the endpoint will wait to regenerate the cursor after it has been killed by the MongoDB server (normal behaviour).

 

(tick)

tailTrackDb

same as endpoint's

Database on which the persistent tail tracker will store its runtime information.

 

(tick)

tailTrackCollection

camelTailTracki ng

Collection on which the persistent tail tracker will store its runtime information.

 

(tick)

tailTrackField

lastTrackingValue

Field in which the persistent tail tracker will store the last tracked value.

 

(tick)

Configuration of database in Spring XML

The following Spring XML creates a bean defining the connection to a MongoDB instance.