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

---
 Home.md | 38 ++++++++++++++++++++++++--------------
 1 file changed, 24 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..4f5ba2b 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,31 @@
-# Deploy the Project on CamelX Platform
+# Spring LDAP
 
-Deploy on CamelX Platform in three steps
+Perform searches in LDAP servers using filters as the message payload.
 
-## 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-ldap` |
+| Support Level | Stable |
+| Labels | security |
+| 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-ldap</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 |
+|------|------|----------|---------|-------------|
+| `templateName` | string | ✓ |  | Name of the Spring LDAP Template bean |
+| `operation` | object | ✓ |  | The LDAP operation to be performed. |
+| `scope` | string |  | `subtree` | The scope of the search operation. |
+| `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. |