Update wiki Home page for json-validator

Home.md

@@ -1,21 +1,39 @@
-# Deploy the Project on CamelX Platform
+# JSON Schema Validator
 
-Deploy on CamelX Platform in three steps
+Validate JSON payloads using NetworkNT JSON Schema.
 
-## 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 | `json-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-json-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 |
+|------|------|----------|---------|-------------|
+| `resourceUri` | string | ✓ |  | Path to the resource. You can prefix with: classpath, file, http, ref, or bean. classpath, file and http loads the resource using these protocols (classpath is default). ref will lookup the resource in the registry. bean will call a method on a bean to be used as the resource. For bean you can specify the method name after dot, eg bean:myBean.myMethod. |
+| `allowContextMapAll` | boolean |  | `false` | Sets whether the context map should allow access to all details. By default only the message body and headers can be accessed. This option can be enabled for full access to the current Exchange and CamelContext. Doing so impose a potential security risk as this opens access to the full power of CamelContext API. |
+| `contentCache` | boolean |  | `false` | Sets whether to use resource content cache or not |
+| `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. |
+| `disabledDeserializationFeatures` | string |  |  | Comma-separated list of Jackson DeserializationFeature enum values which will be disabled for parsing exchange body |
+| `enabledDeserializationFeatures` | string |  |  | Comma-separated list of Jackson DeserializationFeature enum values which will be enabled for parsing exchange body |
+| `errorHandler` | object |  |  | To use a custom ValidatorErrorHandler. The default error handler captures the errors and throws an exception. |
+| `objectMapper` | object |  |  | The used Jackson object mapper |
+| `uriSchemaLoader` | object |  |  | To use a custom schema loader allowing for adding custom format validation. The default implementation will create a schema loader that tries to determine the schema version from the $schema property of the specified schema. |