This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git
commit bc7bb9c81f0d1d0838eec009f9ad8ce22f028e7e Author: Claus Ibsen <[email protected]> AuthorDate: Wed Jul 31 05:21:28 2019 +0200 Regen --- .../modules/ROOT/pages/mock-component.adoc | 9 ------ .../modules/ROOT/pages/mongodb3-component.adoc | 34 ++++++++++++---------- 2 files changed, 18 insertions(+), 25 deletions(-) diff --git a/docs/components/modules/ROOT/pages/mock-component.adoc b/docs/components/modules/ROOT/pages/mock-component.adoc index b5a8bb3..9a11ced 100644 --- a/docs/components/modules/ROOT/pages/mock-component.adoc +++ b/docs/components/modules/ROOT/pages/mock-component.adoc @@ -164,7 +164,6 @@ invoked. This can be configured by setting the == Using assertPeriod -*Available as of Camel 2.7* + When the assertion is satisfied then Camel will stop waiting and continue from the `assertIsSatisfied` method. That means if a new message arrives on the mock endpoint, just a bit later, that arrival @@ -250,8 +249,6 @@ processor tests]. == Mocking existing endpoints -*Available as of Camel 2.7* - Camel now allows you to automatically mock existing endpoints in your Camel routes. @@ -376,8 +373,6 @@ in the constructor for the bean: == Mocking endpoints and skip sending to original endpoint -*Available as of Camel 2.10* - Sometimes you want to easily mock and skip sending to a certain endpoints. So the message is detoured and send to the mock endpoint only. You can now use the `mockEndpointsAndSkip` @@ -402,8 +397,6 @@ include::{examplesdir}/components/camel-test/src/test/java/org/apache/camel/test == Limiting the number of messages to keep -*Available as of Camel 2.10* - The xref:mock-component.adoc[Mock] endpoints will by default keep a copy of every Exchange that it received. So if you test with a lot of messages, then it will consume memory. + @@ -437,8 +430,6 @@ expectations on the 10 retained messages. == Testing with arrival times -*Available as of Camel 2.7* - The xref:mock-component.adoc[Mock] endpoint stores the arrival time of the message as a property on the Exchange. diff --git a/docs/components/modules/ROOT/pages/mongodb3-component.adoc b/docs/components/modules/ROOT/pages/mongodb3-component.adoc index 1b21a39..9c55c50 100644 --- a/docs/components/modules/ROOT/pages/mongodb3-component.adoc +++ b/docs/components/modules/ROOT/pages/mongodb3-component.adoc @@ -185,7 +185,7 @@ xsi:schemaLocation="http://www.springframework.org/schema/context == Sample route The following route defined in Spring XML executes the operation -xref:mongodb3-component.adoc[*dbStats*] on a collection. +<<getDbStats>> on a collection. *Get DB stats for specified collection* @@ -208,7 +208,7 @@ xref:mongodb3-component.adoc[*dbStats*] on a collection. This operation retrieves only one element from the collection whose _id field matches the content of the IN message body. The incoming object can be anything that has an equivalent to a `Bson` type. See -http://bsonspec.org/#/specification[http://bsonspec.org/#/specification] +http://bsonspec.org/spec.html[http://bsonspec.org/spec.html] and http://www.mongodb.org/display/DOCS/Java+Types[http://www.mongodb.org/display/DOCS/Java+Types]. @@ -219,9 +219,9 @@ from("direct:findById") .to("mock:resultFindById"); ------------------------------------------------------------------------------ - -TIP: *Supports optional parameters*. This operation supports specifying a fields filter. See -xref:mongodb3-component.adoc[Specifying optional parameters]. +TIP: *Supports optional parameters*. +This operation supports specifying a fields filter. +See <<Specifying a fields filter (projection)>>. ==== findOneByQuery @@ -229,8 +229,9 @@ Use this operation to retrieve just one element (the first) from the collection matches a MongoDB query. *The query object is extracted `CamelMongoDbCriteria` header*. if the CamelMongoDbCriteria header is null the query object is extracted message body, i.e. it should be of type `Bson` or convertible to -`Bson`. It can be a JSON String or a Hashmap. See xref:mongodb3-component.adoc[#Type conversions] for more info. -you can use the Filters class from MongoDB Driver. +`Bson`. It can be a JSON String or a Hashmap. +See <<Type conversions>> for more info. +You can use the Filters class from MongoDB Driver. Example with no query (returns any object of the collection): @@ -251,8 +252,9 @@ from("direct:findOneByQuery") .to("mock:resultFindOneByQuery"); ------------------------------------------------------------------------------------ -TIP: *Supports optional parameters*. This operation supports specifying a fields projection and/or a sort clause. See -xref:mongodb3-component.adoc[Specifying optional parameters]. +TIP: *Supports optional parameters*. +This operation supports specifying a fields projection and/or a sort clause. +See <<Specifying a fields filter (projection)>>, <<Specifying a sort clause>>. ==== findAll @@ -260,10 +262,9 @@ The `findAll` operation returns all documents matching a query, or none at all, in which case all documents contained in the collection are returned. *The query object is extracted `CamelMongoDbCriteria` header*. if the CamelMongoDbCriteria header is null the query object is extracted -message body, i.e. it should be of type `Bson` or convertible to -`Bson`. It can be -a JSON String or a Hashmap. See xref:mongodb3-component.adoc[#Type conversions] for -more info. +message body, i.e. it should be of type `Bson` or convertible to `Bson`. +It can be a JSON String or a Hashmap. +See <<Type conversions>> for more info. Example with no query (returns all object in the collection): @@ -334,8 +335,9 @@ consideration. |int/Integer consideration. |int/Integer |======================================================================= -TIP: *Supports optional parameters*. This operation supports specifying a fields projection and/or a sort clause. See -xref:mongodb3-component.adoc[Specifying optional parameters]. +TIP: *Supports optional parameters*. +This operation supports specifying a fields projection and/or a sort clause. +See <<Specifying a fields filter (projection)>>, <<Specifying a sort clause>>. ==== count @@ -963,7 +965,7 @@ Because change streams use the aggregation framework, applications can also filt To configure Change Streams Consumer you need to specify `consumerType`, `database`, `collection` and optional JSON property `streamFilter` to filter events. -That JSON property is standart MongoDB `$match` aggregation. +That JSON property is standard MongoDB `$match` aggregation. It could be easily specified using XML DSL configuration: [source,xml]
