Update wiki Home page for spring-redis

Home.md

@@ -1,21 +1,39 @@
-# Deploy the Project on CamelX Platform
+# Spring Redis
 
-Deploy on CamelX Platform in three steps
+Send and receive messages from Redis.
 
-## 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 | `spring-redis` |
+| Support Level | Stable |
+| Labels | cache |
+| 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-spring-redis</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 |
+|------|------|----------|---------|-------------|
+| `host` | string | ✓ |  | The host where Redis server is running. |
+| `port` | integer | ✓ |  | Redis server port number |
+| `channels` | string |  |  | List of topic names or name patterns to subscribe to. Multiple names can be separated by comma. |
+| `command` | object |  | `SET` | Default command, which can be overridden by message header. Notice the consumer only supports the following commands: PSUBSCRIBE and SUBSCRIBE |
+| `connectionFactory` | object |  |  | Reference to a pre-configured RedisConnectionFactory instance to use. |
+| `redisTemplate` | object |  |  | Reference to a pre-configured RedisTemplate instance to use. |
+| `serializer` | object |  |  | Reference to a pre-configured RedisSerializer instance to use. |
+| `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. |
+| `listenerContainer` | object |  |  | Reference to a pre-configured RedisMessageListenerContainer instance to use. |
+| `lazyStartProducer` | boolean |  | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |