Update wiki Home page for validator

Home.md

@@ -1,21 +1,38 @@
-# Deploy the Project on CamelX Platform
+# Validator
 
-Deploy on CamelX Platform in three steps
+Validate the payload using XML Schema and JAXP Validation.
 
-## 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 | `validator` |
+| Support Level | Stable |
+| Labels | core,validation |
+| 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-validator</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 |
+|------|------|----------|---------|-------------|
+| `resourceUri` | string | ✓ |  | URL to a local resource on the classpath, or a reference to lookup a bean in the Registry, or a full URL to a remote resource or resource on the file system which contains the XSD to validate against. |
+| `failOnNullBody` | boolean |  | `true` | Whether to fail if no body exists. |
+| `failOnNullHeader` | boolean |  | `true` | Whether to fail if no header exists when validating against a header. |
+| `headerName` | string |  |  | To validate against a header instead of the message body. |
+| `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. |
+| `errorHandler` | object |  |  | To use a custom org.apache.camel.processor.validation.ValidatorErrorHandler. The default error handler captures the errors and throws an exception. |
+| `resourceResolver` | object |  |  | To use a custom LSResourceResolver. Do not use together with resourceResolverFactory |
+| `resourceResolverFactory` | object |  |  | To use a custom LSResourceResolver which depends on a dynamic endpoint resource URI. The default resource resolver factory returns a resource resolver which can read files from the class path and file system. Do not use together with resourceResolver. |
+| `schemaFactory` | object |  |  | To use a custom javax.xml.validation.SchemaFactory |
+| `schemaLanguage` | string |  | `http://www.w3.org/2001/XMLSchema` | Configures the W3C XML Schema Namespace URI. |
+| `useSharedSchema` | boolean |  | `true` | Whether the Schema instance should be shared or not. This option is introduced to work around a JDK 1.6.x bug. Xerces should not have this issue. |