From 6b41a1a568dcd71f9cf53ef227d98fe0d3ed7ee5 Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:36:20 +0000
Subject: [PATCH] Update wiki Home page for bean-validator

---
 Home.md | 43 +++++++++++++++++++++++++++++--------------
 1 file changed, 29 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..f7b4298 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,36 @@
-# Deploy the Project on CamelX Platform
+# Bean Validator
 
-Deploy on CamelX Platform in three steps
+Validate the message body using the Java Bean Validation API.
 
-## 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 | `bean-validator` |
+| Support Level | Stable |
+| Labels | validation |
+| 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-bean-validator</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 |
+|------|------|----------|---------|-------------|
+| `label` | string | ✓ |  | Where label is an arbitrary text value describing the endpoint |
+| `group` | string |  | `jakarta.validation.groups.Default` | To use a custom validation group |
+| `ignoreXmlConfiguration` | boolean |  | `false` | Whether to ignore data from the META-INF/validation.xml file. |
+| `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. |
+| `constraintValidatorFactory` | object |  |  | To use a custom ConstraintValidatorFactory |
+| `messageInterpolator` | object |  |  | To use a custom MessageInterpolator |
+| `traversableResolver` | object |  |  | To use a custom TraversableResolver |
+| `validationProviderResolver` | object |  |  | To use a a custom ValidationProviderResolver |
+| `validatorFactory` | object |  |  | To use a custom ValidatorFactory |