Update wiki Home page for ignite-events

Home.md

@@ -1,21 +1,35 @@
-# Deploy the Project on CamelX Platform
+# Ignite Events
 
-Deploy on CamelX Platform in three steps
+Receive events from an Ignite cluster by creating a local event listener.
 
-## Step 1: Create a release
+## Metadata
-From the project space, click on **"Create a release"**
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `ignite-events` |
+| Support Level | Stable |
+| Labels | messaging,cache,clustering |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
+## Maven Dependency
-Click on **"Deploy"**
 
-- **Version:** Select the desired release
+```xml
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
+<dependency>
-- **Configuration:** Select the configuration source
+    <groupId>org.apache.camel</groupId>
-- **Resources:** Set CPU and Memory
+    <artifactId>camel-ignite</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
+## Endpoint Properties
-Enable **"Expose"**
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `endpointId` | string |  |  | The endpoint ID (not used). |
+| `clusterGroupExpression` | object |  |  | The cluster group expression. |
+| `events` | string |  | `EVTS_ALL` | The event types to subscribe to as a comma-separated string of event constants as defined in EventType. For example: EVT_CACHE_ENTRY_CREATED,EVT_CACHE_OBJECT_REMOVED,EVT_IGFS_DIR_CREATED. |
+| `propagateIncomingBodyIfNoReturnValue` | boolean |  | `true` | Sets whether to propagate the incoming body if the return type of the underlying Ignite operation is void. |
+| `treatCollectionsAsCacheObjects` | boolean |  | `false` | Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc. |
+| `bridgeErrorHandler` | boolean |  | `false` | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
+| `exceptionHandler` | object |  |  | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
+| `exchangePattern` | object |  |  | Sets the exchange pattern when the consumer creates an exchange. |