From 52378fe73b7c1e0efa1d333c745121f387f79f6b Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:42:29 +0000
Subject: [PATCH] Update wiki Home page for spring-batch

---
 Home.md | 39 +++++++++++++++++++++++++--------------
 1 file changed, 25 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..5fef9c2 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,32 @@
-# Deploy the Project on CamelX Platform
+# Spring Batch
 
-Deploy on CamelX Platform in three steps
+Send messages to Spring Batch for further processing.
 
-## Step 1: Create a release
-From the project space, click on **"Create a release"**
+## Metadata
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `spring-batch` |
+| Support Level | Stable |
+| Labels | workflow |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
-Click on **"Deploy"**
+## Maven Dependency
 
-- **Version:** Select the desired release
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
+```xml
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-spring-batch</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
-Enable **"Expose"**
+## Endpoint Properties
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `jobName` | string | ✓ |  | The name of the Spring Batch job located in the registry. |
+| `jobFromHeader` | boolean |  | `false` | Explicitly defines if the jobName should be taken from the headers instead of the URI. |
+| `jobLauncher` | object |  |  | Explicitly specifies a JobLauncher to be used. |
+| `jobRegistry` | object |  |  | Explicitly specifies a JobRegistry to be used. |
+| `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. |