From 333087fd5cb4a6e2840590f0a255946c58c8844a Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:41:10 +0000
Subject: [PATCH] Update wiki Home page for mapstruct

---
 Home.md | 37 +++++++++++++++++++++++--------------
 1 file changed, 23 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..fdd484c 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,30 @@
-# Deploy the Project on CamelX Platform
+# MapStruct
 
-Deploy on CamelX Platform in three steps
+Type Conversion using Mapstruct
 
-## 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 | `mapstruct` |
+| Support Level | Stable |
+| Labels | transformation |
+| 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-mapstruct</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 |
+|------|------|----------|---------|-------------|
+| `className` | string | ✓ |  | The fully qualified class name of the POJO that mapstruct should convert to (target) |
+| `mandatory` | boolean |  | `true` | Whether there must exist a mapstruct converter to convert to the POJO. |
+| `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. |