camel.apache.org/thymeleaf
1
0
Fork 0
generated from camel.apache.org/component
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update wiki Home page for thymeleaf

gitea_admin 2026-03-11 14:42:48 +00:00
parent 053a43733f
commit 095433d064
1 changed files with 33 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
Home.md

@ -1,21 +1,40 @@
# Deploy the Project on CamelX Platform
# Thymeleaf
Deploy on CamelX Platform in three steps
Transform messages using a Thymeleaf 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 | `thymeleaf` |
| 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-thymeleaf</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. |
| `cacheable` | boolean | | | Whether templates have to be considered cacheable or not. |
| `cacheTimeToLive` | integer | | | The cache Time To Live for templates, expressed in milliseconds. |
| `checkExistence` | boolean | | | Whether a template resources will be checked for existence before being returned. |
| `contentCache` | boolean | | `false` | Sets whether to use resource content cache or not |
| `templateMode` | string | | `HTML` | The template mode to be applied to templates. |
| `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. |
| `encoding` | string | | | The character encoding to be used for reading template resources. |
| `order` | integer | | | The order in which this template will be resolved as part of the resolver chain. |
| `prefix` | string | | | An optional prefix added to template names to convert them into resource names. |
| `resolver` | object | | `CLASS_LOADER` | The type of resolver to be used by the template engine. |
| `suffix` | string | | | An optional suffix added to template names to convert them into resource names. |