From 2615a4f447833d1363b9802087c2cdbdeb380371 Mon Sep 17 00:00:00 2001 From: gitea_admin Date: Wed, 11 Mar 2026 14:42:47 +0000 Subject: [PATCH] Update wiki Home page for thrift --- Home.md | 50 ++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 36 insertions(+), 14 deletions(-) diff --git a/Home.md b/Home.md index 93a012c..121f166 100644 --- a/Home.md +++ b/Home.md @@ -1,21 +1,43 @@ -# Deploy the Project on CamelX Platform +# Thrift -Deploy on CamelX Platform in three steps +Call and expose remote procedures (RPC) with Apache Thrift data format and serialization mechanism. -## 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 | `thrift` | +| Support Level | Stable | +| Labels | rpc,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-thrift + 4.10.2 + +``` -## Step 3: Expose -Enable **"Expose"** +## Endpoint Properties -Choose an **API Gateway** (Internal, Public, etc.) +| Name | Type | Required | Default | Description | +|------|------|----------|---------|-------------| +| `host` | string | ✓ | | The Thrift server host name. This is localhost or 0.0.0.0 (if not defined) when being a consumer or remote server host name when using producer. | +| `port` | integer | ✓ | | The Thrift server port | +| `service` | string | ✓ | | Fully qualified service name from the thrift descriptor file (package dot service definition name) | +| `compressionType` | object | | `NONE` | Protocol compression mechanism type | +| `exchangeProtocol` | object | | `BINARY` | Exchange protocol serialization type | +| `clientTimeout` | integer | | | Client timeout for consumers | +| `maxPoolSize` | integer | | `10` | The Thrift server consumer max thread pool size | +| `poolSize` | integer | | `1` | The Thrift server consumer initial thread pool size | +| `bridgeErrorHandler` | boolean | | `false` | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | +| `exceptionHandler` | object | | | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | +| `exchangePattern` | object | | | Sets the exchange pattern when the consumer creates an exchange. | +| `method` | string | | | The Thrift invoked method name | +| `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. | +| `synchronous` | boolean | | `false` | Sets whether synchronous processing should be strictly used | +| `negotiationType` | object | | `PLAINTEXT` | Security negotiation type | +| `sslParameters` | object | | | Configuration parameters for SSL/TLS security negotiation |