From 02d4af9ebfad958da95b99c9ae20461251179969 Mon Sep 17 00:00:00 2001 From: gitea_admin Date: Wed, 11 Mar 2026 14:41:00 +0000 Subject: [PATCH] Update wiki Home page for language --- Home.md | 44 ++++++++++++++++++++++++++++++-------------- 1 file changed, 30 insertions(+), 14 deletions(-) diff --git a/Home.md b/Home.md index 93a012c..20ebd53 100644 --- a/Home.md +++ b/Home.md @@ -1,21 +1,37 @@ -# Deploy the Project on CamelX Platform +# Language -Deploy on CamelX Platform in three steps +Execute scripts in any of the languages supported by Camel. -## 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 | `language` | +| Support Level | Stable | +| Labels | core,script | +| 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-language + 4.10.2 + +``` -## Step 3: Expose -Enable **"Expose"** +## Endpoint Properties -Choose an **API Gateway** (Internal, Public, etc.) +| Name | Type | Required | Default | Description | +|------|------|----------|---------|-------------| +| `languageName` | string | ✓ | | Sets the name of the language to use | +| `resourceUri` | string | | | Path to the resource, or a reference to lookup a bean in the Registry to use as the resource | +| `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. | +| `binary` | boolean | | `false` | Whether the script is binary content or text content. By default the script is read as text content (eg java.lang.String) | +| `cacheScript` | boolean | | `false` | Whether to cache the compiled script and reuse Notice reusing the script can cause side effects from processing one Camel org.apache.camel.Exchange to the next org.apache.camel.Exchange. | +| `contentCache` | boolean | | `true` | Sets whether to use resource content cache or not | +| `resultType` | string | | | Sets the class of the result type (type from output) | +| `script` | string | | | Sets the script to execute | +| `transform` | boolean | | `true` | Whether or not the result of the script should be used as message body. This options is default true. | +| `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. |