This is an automated email from the ASF dual-hosted git repository. orpiske pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit 4372baf92a06be3385ce947b79bdb69a4e923711 Author: Otavio Rodolfo Piske <[email protected]> AuthorDate: Tue Feb 20 18:11:28 2024 +0100 CAMEL-20410: documentation fixes for camel-hazelcast - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../main/docs/hazelcast-atomicvalue-component.adoc | 57 +++++++++++---- .../main/docs/hazelcast-instance-component.adoc | 4 +- .../src/main/docs/hazelcast-list-component.adoc | 6 +- .../src/main/docs/hazelcast-map-component.adoc | 83 +++++++++++++++------- .../main/docs/hazelcast-multimap-component.adoc | 53 +++++++++----- .../src/main/docs/hazelcast-queue-component.adoc | 4 +- .../docs/hazelcast-replicatedmap-component.adoc | 40 +++++++---- .../main/docs/hazelcast-ringbuffer-component.adoc | 11 ++- .../src/main/docs/hazelcast-seda-component.adoc | 21 ++++-- .../src/main/docs/hazelcast-set-component.adoc | 4 +- .../src/main/docs/hazelcast-summary.adoc | 20 +++--- .../src/main/docs/hazelcast-topic-component.adoc | 2 +- 12 files changed, 206 insertions(+), 99 deletions(-) diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc index 99aad377a26..4fa4e49e432 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-atomicvalue-component.adoc @@ -51,8 +51,11 @@ include::partial$component-endpoint-headers.adoc[] === Sample for *set*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ----------------------------------------------------------------------------------------- from("direct:set") @@ -60,8 +63,8 @@ from("direct:set") .toF("hazelcast-%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX); ----------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -73,13 +76,18 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + Provide the value to set inside the message body (here the value is 10): `template.sendBody("direct:set", 10);` === Sample for *get*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:get") @@ -87,8 +95,8 @@ from("direct:get") .toF("hazelcast-%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -100,12 +108,18 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + You can get the number with `long body = template.requestBody("direct:get", null, Long.class);`. === Sample for *increment*: -Java DSL: +[tabs] +==== + +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------------ @@ -114,8 +128,8 @@ from("direct:increment") .toF("hazelcast-%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX); ------------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -127,12 +141,18 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + The actual value (after increment) will be provided inside the message body. === Sample for *decrement*: -Java DSL: +[tabs] +==== + +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------------ @@ -141,8 +161,8 @@ from("direct:decrement") .toF("hazelcast-%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX); ------------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -154,12 +174,18 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + The actual value (after decrement) will be provided inside the message body. === Sample for *destroy* -Java DSL: +[tabs] +==== + +Java DSL:: ++ [source,java] ---------------------------------------------------------------------------------------- @@ -168,8 +194,8 @@ from("direct:destroy") .toF("hazelcast-%sfoo", HazelcastConstants.ATOMICNUMBER_PREFIX); ---------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -181,5 +207,6 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== include::spring-boot:partial$starter.adoc[] diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc index 45ed47ea30b..28c3d082365 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-instance-component.adoc @@ -16,7 +16,7 @@ *{component-header}* The http://www.hazelcast.com/[Hazelcast] instance component is one of Camel Hazelcast Components which allows you to consume join/leave events of the cache instance in the cluster. -Hazelcast makes sense in one single "server node", but it's extremly powerful in a clustered environment. +Hazelcast makes sense in one single "server node", but it's extremely powerful in a clustered environment. // component-configure options: START @@ -34,7 +34,7 @@ include::partial$component-endpoint-options.adoc[] == instance consumer - from("hazelcast-instance:foo") -The instance consumer fires if a new cache instance will join or leave the cluster. +The instance consumer fires if a new cache instance joins or leaves the cluster. Here's a sample: diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc index fd97c4cf39c..67fffbe245c 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-list-component.adoc @@ -15,7 +15,7 @@ *{component-header}* -The http://www.hazelcast.com/[Hazelcast] List component is one of Camel Hazelcast Components which allows you to access Hazelcast distributed list. +The http://www.hazelcast.com/[Hazelcast] List component is one of Camel Hazelcast Components which allows you to access a Hazelcast distributed list. == Options @@ -35,7 +35,7 @@ include::partial$component-endpoint-options.adoc[] == List producer – to(“hazelcast-list:foo”) -The list producer provides 8 operations: +The list producer provides eight operations: * add * addAll @@ -93,7 +93,7 @@ purpose. == List consumer – from(“hazelcast-list:foo”) -The list consumer provides 2 operations: +The list consumer provides two operations: * add * remove diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc index de08673a920..287604bfa97 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc @@ -15,7 +15,7 @@ *{component-header}* -The http://www.hazelcast.com/[Hazelcast] Map component is one of Camel Hazelcast Components which allows you to access Hazelcast distributed map. +The http://www.hazelcast.com/[Hazelcast] Map component is one of Camel Hazelcast Components which allows you to access a Hazelcast distributed map. == Options @@ -36,7 +36,7 @@ include::partial$component-endpoint-options.adoc[] == Map cache producer - to("hazelcast-map:foo") -If you want to store a value in a map you can use the map cache +If you want to store a value in a map, you can use the map cache producer. The map cache producer provides follow operations specified by *CamelHazelcastOperationType* header: @@ -68,8 +68,11 @@ template.sendBodyAndHeader("direct:[put|get|update|delete|query|evict]", "my-foo === Sample for *put*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:put") @@ -77,8 +80,8 @@ from("direct:put") .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -90,9 +93,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + Sample for *put* with eviction: -Java DSL: +[tabs] +==== + +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ @@ -103,8 +112,8 @@ from("direct:put") .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -122,11 +131,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== === Sample for *get*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:get") @@ -135,8 +148,8 @@ from("direct:get") .to("seda:out"); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -149,10 +162,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *update*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] --------------------------------------------------------------------------------------- from("direct:update") @@ -160,8 +178,8 @@ from("direct:update") .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX); --------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -173,9 +191,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *delete*: -Java DSL: +[tabs] +==== + +Java DSL:: ++ [source,java] --------------------------------------------------------------------------------------- @@ -184,8 +208,8 @@ from("direct:delete") .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX); --------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -197,10 +221,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *query* -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] -------------------------------------------------------------------------------------- from("direct:query") @@ -209,8 +238,8 @@ from("direct:query") .to("seda:out"); -------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -223,7 +252,9 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- -For the query operation Hazelcast offers a SQL like syntax to query your +==== + +For the query operation Hazelcast offers an SQL like syntax to query your distributed map. [source,java] @@ -236,8 +267,8 @@ template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1); == Map cache consumer - from("hazelcast-map:foo") Hazelcast provides event listeners on their data grid. If you want to be -notified if a cache will be manipulated, you can use the map consumer. -There're 4 events: *put*, *update*, *delete* and *envict*. The event +notified if a cache is manipulated, you can use the map consumer. +There are four events: *put*, *update*, *delete* and *envict*. The event type will be stored in the "*hazelcast.listener.action*" header variable. The map consumer provides some additional information inside these variables: @@ -252,13 +283,13 @@ Header Variables inside the response message: |`CamelHazelcastListenerType` |`String` |the map consumer sets here "cachelistener" -|`CamelHazelcastListenerAction` |`String` |type of event - here *added*, *updated*, *envicted* and *removed*. +|`CamelHazelcastListenerAction` |`String` |type of event (*added*, *updated*, *envicted* and *removed*). |`CamelHazelcastObjectId` |`String` |the oid of the object -|`CamelHazelcastCacheName` |`String` |the name of the cache - e.g. "foo" +|`CamelHazelcastCacheName` |`String` |the name of the cache (e.g., "foo") -|`CamelHazelcastCacheType` |`String` |the type of the cache - here map +|`CamelHazelcastCacheType` |`String` |the type of the cache (e.g., map) |======================================================================= The object value will be stored within *put* and *update* actions inside diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc index d133a8b33f3..7f294f6543c 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-multimap-component.adoc @@ -38,7 +38,7 @@ include::partial$component-endpoint-options.adoc[] A multimap is a cache where you can store n values to one key. -The multimap producer provides 8 operations: +The multimap producer provides eight operations: * put * get @@ -55,8 +55,11 @@ include::partial$component-endpoint-headers.adoc[] === Sample for *put*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:put") @@ -64,8 +67,8 @@ from("direct:put") .to(String.format("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX)); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -78,9 +81,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *removevalue*: -Java DSL: +[tabs] +==== + +Java DSL:: ++ [source,java] -------------------------------------------------------------------------------------------- @@ -89,8 +98,8 @@ from("direct:removevalue") .toF("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX); -------------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -103,15 +112,20 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + To remove a value you have to provide the value you want to remove inside the message body. If you have a multimap object -\{`key: "4711" values: { "my-foo", "my-bar"`}} you have to put "my-foo" -inside the message body to remove the "my-foo" value. +`\{`key: "4711" values: { "my-foo", "my-bar"`}}` you have to put `my-foo` +inside the message body to remove the `my-foo` value. === Sample for *get*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:get") @@ -120,8 +134,8 @@ from("direct:get") .to("seda:out"); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -135,10 +149,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *delete*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] --------------------------------------------------------------------------------------- from("direct:delete") @@ -146,8 +165,8 @@ from("direct:delete") .toF("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX); --------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -160,7 +179,9 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- -you can call them in your test class with: +==== + +You can call them in your test class with: [source,java] ------------------------------------------------------------------------------------------------------------------ diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc index c2191782e5d..78ce518d615 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-queue-component.adoc @@ -170,10 +170,10 @@ Sample for *Poll* mode fromF("hazelcast-%sfoo?queueConsumerMode=Poll", HazelcastConstants.QUEUE_PREFIX)).to("mock:result"); ------------------------------------------------------------------------------------------- -In this way the consumer will poll the queue and return the head of the queue or null after a timeout. +In this way, the consumer will poll the queue and return the head of the queue or null after a timeout. -In Listen mode instead the consumer will listen for events on queue. +In Listen mode instead, the consumer will listen for events on queue. The queue consumer in Listen mode provides 2 operations: * add diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc index 6b68621d564..b7413e842db 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-replicatedmap-component.adoc @@ -50,8 +50,11 @@ include::partial$component-endpoint-headers.adoc[] === Sample for *put*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:put") @@ -59,8 +62,8 @@ from("direct:put") .to(String.format("hazelcast-%sbar", HazelcastConstants.REPLICATEDMAP_PREFIX)); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -73,10 +76,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *get*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:get") @@ -85,8 +93,8 @@ from("direct:get") .to("seda:out"); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -100,10 +108,15 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *delete*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] --------------------------------------------------------------------------------------- from("direct:delete") @@ -111,8 +124,8 @@ from("direct:delete") .toF("hazelcast-%sbar", HazelcastConstants.REPLICATEDMAP_PREFIX); --------------------------------------------------------------------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -124,8 +137,9 @@ Spring DSL: <to uri="hazelcast-replicatedmap:foo" /> </route> ----------------------------------------------------------------------------------------------- +==== -you can call them in your test class with: +You can call them in your test class with: [source,java] ------------------------------------------------------------------------------------------------------------ @@ -134,7 +148,7 @@ template.sendBodyAndHeader("direct:[put|get|delete|clear]", "my-foo", HazelcastC == replicatedmap cache consumer -For the multimap cache this component provides the same listeners / +For the multimap cache, this component provides the same listeners / variables as for the map cache consumer (except the update and enviction listener). The only difference is the *multimap* prefix inside the URI. Here is a sample: @@ -171,9 +185,9 @@ Header Variables inside the response message: |`CamelHazelcastObjectId` |`String` | the oid of the object -|`CamelHazelcastCacheName` |`String` |the name of the cache - e.g. "foo" +|`CamelHazelcastCacheName` |`String` |the name of the cache (e.g., "foo") -|`CamelHazelcastCacheType` |`String` |the type of the cache - here replicatedmap +|`CamelHazelcastCacheType` |`String` |the type of the cache (e.g., replicatedmap) |======================================================================= diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc index c2313bc5a48..a940136c970 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-ringbuffer-component.adoc @@ -49,8 +49,11 @@ include::partial$component-endpoint-headers.adoc[] === Sample for *put*: -Java DSL: +[tabs] +==== +Java DSL:: ++ [source,java] ------------------------------------------------------------------------------------ from("direct:put") @@ -58,8 +61,8 @@ from("direct:put") .to(String.format("hazelcast-%sbar", HazelcastConstants.RINGBUFFER_PREFIX)); ------------------------------------------------------------------------------------ -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------------------------------------------------------------------- <route> @@ -72,6 +75,8 @@ Spring DSL: </route> ----------------------------------------------------------------------------------------------- +==== + === Sample for *readonce from head*: Java DSL: diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc index 190387b80ba..e3d476bd1ac 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-seda-component.adoc @@ -42,16 +42,19 @@ specified queue. include::partial$component-endpoint-headers.adoc[] // component headers: END -Java DSL : +[tabs] +==== +Java DSL:: ++ [source,java] -------------------------- from("direct:foo") .to("hazelcast-seda:foo"); -------------------------- -Spring DSL : - +Spring XML:: ++ [source,xml] ---------------------------------- <route> @@ -60,21 +63,26 @@ Spring DSL : </route> ---------------------------------- +==== + == SEDA consumer – from(“hazelcast-seda:foo”) The SEDA consumer provides no operations. You only retrieve data from the specified queue. -Java DSL : +[tabs] +==== +Java DSL:: ++ [source,java] -------------------------- from("hazelcast-seda:foo") .to("mock:result"); -------------------------- -Spring DSL: - +Spring XML:: ++ [source,xml] ----------------------------------- <route> @@ -83,5 +91,6 @@ Spring DSL: </route> ----------------------------------- +==== include::spring-boot:partial$starter.adoc[] diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc index 7710831a2a6..402c6b63141 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-set-component.adoc @@ -15,7 +15,7 @@ *{component-header}* -The http://www.hazelcast.com/[Hazelcast] Set component is one of Camel Hazelcast Components which allows you to access Hazelcast distributed set. +The http://www.hazelcast.com/[Hazelcast] Set component is one of Camel Hazelcast Components which allows you to access a Hazelcast distributed set. // component-configure options: START @@ -33,7 +33,7 @@ include::partial$component-endpoint-options.adoc[] == set cache producer -The set producer provides 7 operations: +The set producer provides seven operations: * add * removeAll diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-summary.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-summary.adoc index d326a2a77c2..df2f4aafac8 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-summary.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-summary.adoc @@ -9,15 +9,15 @@ The *hazelcast-* component allows you to work with the http://www.hazelcast.com[Hazelcast] distributed data grid / cache. -Hazelcast is a in memory data grid, entirely written in Java (single -jar). It offers a great palette of different data stores like map, multi -map (same key, n values), queue, list and atomic number. The main reason +Hazelcast is an in-memory data grid, entirely written in Java (single +jar). It offers a great palette of different data stores like map, +multimap (same key, n values), queue, list and atomic number. The main reason to use Hazelcast is its simple cluster support. If you have enabled -multicast on your network you can run a cluster with hundred nodes with -no extra configuration. Hazelcast can simply configured to add +multicast on your network, you can run a cluster with a hundred nodes with +no extra configuration. Hazelcast can simply configure to add additional features like n copies between nodes (default is 1), cache -persistence, network configuration (if needed), near cache, eviction -and so on. For more information consult the Hazelcast documentation on +persistence, network configuration (if needed), near cache, eviction, +and so on. For more information, consult the Hazelcast documentation on http://www.hazelcast.com/docs.jsp[http://www.hazelcast.com/docs.jsp]. == {doctitle} components @@ -112,7 +112,7 @@ for this component: === Configuring HazelcastInstance on component You can also configure the hazelcast instance on the component which will then be used by all hazelcast endpoints. -In the example above we setup this for the hazelcast map component and setup hazelcast via verbose `<bean>` configurations. +In the example above we set up this for the hazelcast map component and setup hazelcast via verbose `<bean>` configurations. [source,xml] ------------------------------------------------------------------------------ @@ -136,12 +136,12 @@ In the example above we setup this for the hazelcast map component and setup haz == Publishing hazelcast instance as an OSGI service -If operating in an OSGI container and you would want to use one instance +If operating in an OSGI container, and you would want to use one instance of hazelcast across all bundles in the same container. You can publish the instance as an OSGI service and bundles using the cache al need is to reference the service in the hazelcast endpoint. -=== Bundle A create an instance and publishes it as an OSGI service +=== Bundle A create an instance and publish it as an OSGI service [source,xml] -------------------------------------------------------------------------------------------------------- diff --git a/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc b/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc index 71bcedb705e..5189582fda9 100644 --- a/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc +++ b/components/camel-hazelcast/src/main/docs/hazelcast-topic-component.adoc @@ -55,7 +55,7 @@ from("direct:add") The topic consumer provides only one operation (received). This component is supposed to support multiple consumption as it's expected -when it comes to topics so you are free to have as much consumers as you +when it comes to topics, so you are free to have as many consumers as you need on the same hazelcast topic. [source,java]
