From 190d792635597bb91c4f67edac8516e456fa8cff Mon Sep 17 00:00:00 2001 From: gitea_admin Date: Wed, 11 Mar 2026 14:42:57 +0000 Subject: [PATCH] Update wiki Home page for velocity --- Home.md | 42 ++++++++++++++++++++++++++++-------------- 1 file changed, 28 insertions(+), 14 deletions(-) diff --git a/Home.md b/Home.md index 93a012c..a063edf 100644 --- a/Home.md +++ b/Home.md @@ -1,21 +1,35 @@ -# Deploy the Project on CamelX Platform +# Velocity -Deploy on CamelX Platform in three steps +Transform messages using a Velocity template. -## 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 | `velocity` | +| 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 + + org.apache.camel + camel-velocity + 4.10.2 + +``` -## 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. | +| `allowTemplateFromHeader` | boolean | | `false` | Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care. | +| `contentCache` | boolean | | `false` | Sets whether to use resource content cache or not | +| `encoding` | string | | | Character encoding of the resource content. | +| `loaderCache` | boolean | | `true` | Enables / disables the velocity resource loader cache which is enabled by default | +| `propertiesFile` | string | | | The URI of the properties file which is used for VelocityEngine initialization. | +| `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. |