You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2026/08/11 11:32:08 UTC
(camel-website) branch main updated: Move xsd to correct folder
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/main by this push:
new 6cf3086a Move xsd to correct folder
6cf3086a is described below
commit 6cf3086a96c01468c70b0b17d091f273e538d123
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Tue Aug 11 13:31:55 2026 +0200
Move xsd to correct folder
---
.../camel-spring-4.22.0.xsd} | 0
static/schema/spring/camel-spring.xsd | 7816 ++++++++------------
2 files changed, 2957 insertions(+), 4859 deletions(-)
diff --git a/static/schema/spring-xml/camel-spring-xml-4.22.0.xsd b/static/schema/spring/camel-spring-4.22.0.xsd
similarity index 100%
rename from static/schema/spring-xml/camel-spring-xml-4.22.0.xsd
rename to static/schema/spring/camel-spring-4.22.0.xsd
diff --git a/static/schema/spring/camel-spring.xsd b/static/schema/spring/camel-spring.xsd
index 673fe0f7..1cd46566 100644
--- a/static/schema/spring/camel-spring.xsd
+++ b/static/schema/spring/camel-spring.xsd
@@ -1,9 +1,19 @@
<?xml version="1.0" encoding="UTF-8"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://camel.apache.org/schema/spring" elementFormDefault="qualified" targetNamespace="http://camel.apache.org/schema/spring" version="1.0">
+ <xs:element name="a2aSubTask" type="tns:a2ASubTaskDefinition">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Groups route steps and emits A2A (Agent-to-Agent) protocol progress events before, after, or when the grouped work fails
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
<xs:element name="aggregate" type="tns:aggregateDefinition">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Aggregates many messages into a single message
+Collects and combines related messages into a single message using a correlation expression and an aggregation strategy.
+Messages are grouped into buckets by correlation key and released when a completion condition is met.
]]>
</xs:documentation>
</xs:annotation>
@@ -12,7 +22,7 @@ Aggregates many messages into a single message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest security basic auth definition
+Configures API key authentication for a REST service
]]>
</xs:documentation>
</xs:annotation>
@@ -21,7 +31,7 @@ Rest security basic auth definition
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encode and decode data structures using Abstract Syntax Notation One (ASN.1).
+Encode and decode data structures using Abstract Syntax Notation One (ASN.1)
]]>
</xs:documentation>
</xs:annotation>
@@ -30,7 +40,7 @@ Encode and decode data structures using Abstract Syntax Notation One (ASN.1).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Serialize and deserialize messages using Apache Avro binary data format.
+Serialize and deserialize messages using Apache Avro binary data format
]]>
</xs:documentation>
</xs:annotation>
@@ -39,7 +49,7 @@ Serialize and deserialize messages using Apache Avro binary data format.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Transform strings to various 1D/2D barcode bitmap formats and back.
+Transform strings to various 1D/2D barcode bitmap formats and back
]]>
</xs:documentation>
</xs:annotation>
@@ -48,7 +58,7 @@ Transform strings to various 1D/2D barcode bitmap formats and back.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encode and decode data using Base64.
+Encode and decode data using Base64
]]>
</xs:documentation>
</xs:annotation>
@@ -57,7 +67,7 @@ Encode and decode data using Base64.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest security basic auth definition
+Configures HTTP Basic authentication for a REST service
]]>
</xs:documentation>
</xs:annotation>
@@ -66,7 +76,8 @@ Rest security basic auth definition
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Configures batch-processing resequence eip.
+Configures the batch-processing mode of the Resequence EIP, which collects messages into a batch and sorts them before
+releasing
]]>
</xs:documentation>
</xs:annotation>
@@ -75,7 +86,8 @@ Configures batch-processing resequence eip.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Calls a Java bean
+Invokes a method on a Java bean, with automatic parameter binding from the message body, headers, and exchange
+properties
]]>
</xs:documentation>
</xs:annotation>
@@ -84,7 +96,8 @@ Calls a Java bean
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Define custom beans that can be used in your Camel routes and in general.
+Defines a custom bean that can be used in Camel routes and other beans. The bean is created by a factory class or
+method.
]]>
</xs:documentation>
</xs:annotation>
@@ -102,7 +115,7 @@ Spring specific DefaultCamelBeanPostProcessor which uses Spring BeanPostProcesso
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal Java beans to and from flat files (such as CSV, delimited, or fixed length formats).
+Marshal and unmarshal Java beans to and from flat files (such as CSV, delimited, or fixed length formats)
]]>
</xs:documentation>
</xs:annotation>
@@ -111,8 +124,7 @@ Marshal and unmarshal Java beans to and from flat files (such as CSV, delimited,
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Container for beans, routes, and more. Important this is only supported when using XML DSL with camel-xml-io-dsl. This
-is NOT for the classic old Spring XML DSL used by Camel 1.x/2.x.
+Container element for defining beans, routes, and other elements using XML DSL with camel-xml-io-dsl
]]>
</xs:documentation>
</xs:annotation>
@@ -121,7 +133,7 @@ is NOT for the classic old Spring XML DSL used by Camel 1.x/2.x.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest security bearer token authentication definition
+Configures Bearer token authentication for a REST service
]]>
</xs:documentation>
</xs:annotation>
@@ -131,25 +143,7 @@ Rest security bearer token authentication definition
<xs:documentation xml:lang="en">
<![CDATA[
Marshal and unmarshal Java beans from and to flat payloads (such as CSV, delimited, fixed length formats, or FIX
-messages).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="blacklistServiceFilter" type="tns:blacklistServiceCallServiceFilterConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="cachingServiceDiscovery" type="tns:cachingServiceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+messages)
]]>
</xs:documentation>
</xs:annotation>
@@ -158,8 +152,8 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Root tag for Camel application, that can contain beans, routes, and more. Important this is only supported when using
-XML DSL with camel-xml-io-dsl. This is NOT for the classic old Spring XML DSL used by Camel 1.x/2.x.
+Root element for a Camel application defined using XML DSL with camel-xml-io-dsl, containing beans, routes, and
+configuration
]]>
</xs:documentation>
</xs:annotation>
@@ -177,7 +171,7 @@ CamelContext using XML configuration.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Unmarshal a CBOR payload to POJO and back.
+Unmarshal a CBOR payload to POJO and back
]]>
</xs:documentation>
</xs:annotation>
@@ -186,7 +180,8 @@ Unmarshal a CBOR payload to POJO and back.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route messages based on a series of predicates
+Routes messages to different steps based on a series of conditions (predicates), similar to if-elseif-else in Java. Each
+condition is evaluated in order until one matches.
]]>
</xs:documentation>
</xs:annotation>
@@ -195,7 +190,8 @@ Route messages based on a series of predicates
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route messages in a fault tolerance way using Circuit Breaker
+Wraps message processing with a circuit breaker for fault tolerance. Prevents cascading failures by short-circuiting
+calls to an unhealthy service and routing to a fallback
]]>
</xs:documentation>
</xs:annotation>
@@ -204,26 +200,8 @@ Route messages in a fault tolerance way using Circuit Breaker
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The Claim Check EIP allows you to replace message content with a claim check (a unique key), which can be used to
-retrieve the message content at a later time.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="combinedServiceDiscovery" type="tns:combinedServiceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="combinedServiceFilter" type="tns:combinedServiceCallServiceFilterConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+Temporarily stores the message content and replaces it with a claim check key, allowing the content to be retrieved
+later in the route. Useful for reducing memory when large payloads pass through processing steps that don't need them.
]]>
</xs:documentation>
</xs:annotation>
@@ -232,16 +210,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A fixed value set only once during the route startup.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="consulServiceDiscovery" type="tns:consulServiceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+A fixed value set only once during the route startup
]]>
</xs:documentation>
</xs:annotation>
@@ -259,7 +228,7 @@ Configures a ConsumerTemplate
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Scans for Java org.apache.camel.builder.RouteBuilder instances in the context org.apache.camel.spi.Registry .
+Scans for RouteBuilder instances in the Camel registry to auto-discover and register routes
]]>
</xs:documentation>
</xs:annotation>
@@ -268,7 +237,7 @@ Scans for Java org.apache.camel.builder.RouteBuilder instances in the context or
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Converts the message body to another type
+Converts the message body to a specified Java type using Camel's built-in type converters
]]>
</xs:documentation>
</xs:annotation>
@@ -277,7 +246,7 @@ Converts the message body to another type
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Converts the message header to another type
+Converts a message header value to a specified Java type using Camel's built-in type converters
]]>
</xs:documentation>
</xs:annotation>
@@ -286,7 +255,7 @@ Converts the message header to another type
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Converts the variable to another type
+Converts a variable value to a specified Java type using Camel's built-in type converters
]]>
</xs:documentation>
</xs:annotation>
@@ -295,7 +264,7 @@ Converts the variable to another type
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encrypt and decrypt messages using Java Cryptography Extension (JCE).
+Encrypt and decrypt messages using Java Cryptography Extension (JCE)
]]>
</xs:documentation>
</xs:annotation>
@@ -304,7 +273,7 @@ Encrypt and decrypt messages using Java Cryptography Extension (JCE).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluate a compiled simple expression.
+Deprecated: Evaluate a compiled simple expression
]]>
</xs:documentation>
</xs:annotation>
@@ -313,7 +282,7 @@ Evaluate a compiled simple expression.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Handle CSV (Comma Separated Values) payloads.
+Handle CSV (Comma Separated Values) payloads
]]>
</xs:documentation>
</xs:annotation>
@@ -322,7 +291,7 @@ Handle CSV (Comma Separated Values) payloads.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Delegate to a custom org.apache.camel.spi.DataFormat implementation via Camel registry.
+Delegates to a custom DataFormat implementation looked up from the Camel registry by name
]]>
</xs:documentation>
</xs:annotation>
@@ -331,16 +300,7 @@ Delegate to a custom org.apache.camel.spi.DataFormat implementation via Camel re
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom load balancer implementation.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="customServiceFilter" type="tns:customServiceCallServiceFilterConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+References a custom load balancer implementation from the registry
]]>
</xs:documentation>
</xs:annotation>
@@ -349,7 +309,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom transformer on a route level.
+References a custom data type transformer implementation from the registry for route-level transformations
]]>
</xs:documentation>
</xs:annotation>
@@ -358,7 +318,7 @@ To use a custom transformer on a route level.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom validator on the route level.
+References a custom data type validator implementation from the registry for route-level validation
]]>
</xs:documentation>
</xs:annotation>
@@ -367,9 +327,7 @@ To use a custom validator on the route level.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Represents a org.apache.camel.processor.transformer.DataFormatTransformer which leverages
-org.apache.camel.spi.DataFormat to perform transformation. One of the DataFormat 'ref' or DataFormat 'type' needs to be
-specified.
+Uses a Camel data format to perform data type transformation between input and output types
]]>
</xs:documentation>
</xs:annotation>
@@ -378,7 +336,7 @@ specified.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Configure data formats.
+Container for defining data format configurations
]]>
</xs:documentation>
</xs:annotation>
@@ -387,7 +345,7 @@ Configure data formats.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use DataSonnet scripts for message transformations.
+To use DataSonnet scripts for message transformations
]]>
</xs:documentation>
</xs:annotation>
@@ -396,7 +354,7 @@ To use DataSonnet scripts for message transformations.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Error handler with dead letter queue.
+Error handler that moves failed messages to a dead letter endpoint after exhausting redelivery attempts
]]>
</xs:documentation>
</xs:annotation>
@@ -405,16 +363,7 @@ Error handler with dead letter queue.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The default error handler.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="defaultLoadBalancer" type="tns:defaultServiceCallServiceLoadBalancerConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+The default error handler that supports redelivery with configurable retry policies and delay patterns
]]>
</xs:documentation>
</xs:annotation>
@@ -423,7 +372,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Delays processing for a specified length of time
+Delays message processing for a specified duration, which can be a fixed value or computed dynamically per message
]]>
</xs:documentation>
</xs:annotation>
@@ -432,7 +381,7 @@ Delays processing for a specified length of time
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest DELETE command
+Defines an HTTP DELETE operation in the REST DSL
]]>
</xs:documentation>
</xs:annotation>
@@ -441,16 +390,7 @@ Rest DELETE command
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Transforms fixed format data such as EDI message from/to XML using a Data Format Description Language (DFDL).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="dnsServiceDiscovery" type="tns:dnsServiceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+Transforms fixed format data such as EDI message from/to XML using a Data Format Description Language (DFDL)
]]>
</xs:documentation>
</xs:annotation>
@@ -459,7 +399,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Catches exceptions as part of a try, catch, finally block
+Catches specific exceptions within a doTry block, allowing fine-grained exception handling within the route
]]>
</xs:documentation>
</xs:annotation>
@@ -468,7 +408,7 @@ Catches exceptions as part of a try, catch, finally block
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Path traversed when a try, catch, finally block exits
+Defines steps to always execute after a doTry block completes, regardless of whether an exception was thrown or caught
]]>
</xs:documentation>
</xs:annotation>
@@ -477,7 +417,7 @@ Path traversed when a try, catch, finally block exits
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marks the beginning of a try, catch, finally block
+Wraps route steps in a try-catch-finally block for fine-grained exception handling within the route
]]>
</xs:documentation>
</xs:annotation>
@@ -486,7 +426,8 @@ Marks the beginning of a try, catch, finally block
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route messages based on dynamic rules
+Routes a message step-by-step through a series of endpoints, determined dynamically by calling an expression repeatedly.
+The expression is called after each hop and returns the next endpoint, or null to stop.
]]>
</xs:documentation>
</xs:annotation>
@@ -504,7 +445,7 @@ Camel endpoint configuration
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a Camel endpoint to perform transformation on the route level.
+Uses a Camel endpoint to perform data type transformation by sending the message through the endpoint
]]>
</xs:documentation>
</xs:annotation>
@@ -513,7 +454,7 @@ To use a Camel endpoint to perform transformation on the route level.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a Camel endpoint to perform validation on the route level.
+Uses a Camel endpoint to perform data type validation by sending the message through the endpoint
]]>
</xs:documentation>
</xs:annotation>
@@ -522,7 +463,8 @@ To use a Camel endpoint to perform validation on the route level.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Enriches a message with data from a secondary resource
+Enriches the message with additional data obtained by sending to another endpoint using request-reply. The reply is
+merged into the original message using an aggregation strategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -531,7 +473,7 @@ Enriches a message with data from a secondary resource
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Camel error handling.
+Configures error handling strategy for routes, controlling how failed exchanges are handled and redelivered
]]>
</xs:documentation>
</xs:annotation>
@@ -540,7 +482,7 @@ Camel error handling.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Gets a property from the Exchange.
+Gets a property from the Exchange
]]>
</xs:documentation>
</xs:annotation>
@@ -559,7 +501,7 @@ A useful base class for an expression
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-In case of failures the exchange will be tried on the next endpoint.
+Load balancer that tries the next endpoint in case of failure, cycling through available endpoints until one succeeds
]]>
</xs:documentation>
</xs:annotation>
@@ -568,7 +510,8 @@ In case of failures the exchange will be tried on the next endpoint.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-MicroProfile Fault Tolerance Circuit Breaker EIP configuration
+Configures MicroProfile Fault Tolerance settings for the Circuit Breaker EIP, such as timeout, bulkhead, and retry
+parameters
]]>
</xs:documentation>
</xs:annotation>
@@ -577,7 +520,7 @@ MicroProfile Fault Tolerance Circuit Breaker EIP configuration
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshall and unmarshall FHIR objects to/from JSON.
+Marshall and unmarshall FHIR objects to/from JSON
]]>
</xs:documentation>
</xs:annotation>
@@ -586,7 +529,7 @@ Marshall and unmarshall FHIR objects to/from JSON.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshall and unmarshall FHIR objects to/from XML.
+Marshall and unmarshall FHIR objects to/from XML
]]>
</xs:documentation>
</xs:annotation>
@@ -595,7 +538,8 @@ Marshall and unmarshall FHIR objects to/from XML.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Filter out messages based using a predicate
+Filters messages using a predicate expression. Messages matching the predicate continue processing; non-matching
+messages are skipped.
]]>
</xs:documentation>
</xs:annotation>
@@ -605,7 +549,7 @@ Filter out messages based using a predicate
<xs:documentation xml:lang="en">
<![CDATA[
Marshal and unmarshal Java lists and maps to/from flat files (such as CSV, delimited, or fixed length formats) using
-Flatpack library.
+Flatpack library
]]>
</xs:documentation>
</xs:annotation>
@@ -632,7 +576,7 @@ Serialize and deserialize messages using Apache Fory
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Act as a message source as input to a route
+Defines the consumer endpoint that acts as the input source for a route
]]>
</xs:documentation>
</xs:annotation>
@@ -641,7 +585,7 @@ Act as a message source as input to a route
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest GET command
+Defines an HTTP GET operation in the REST DSL
]]>
</xs:documentation>
</xs:annotation>
@@ -650,7 +594,7 @@ Rest GET command
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Models a string key/value pair for configuring some global options on a Camel context such as max debug log length.
+Defines a single global configuration option as a key/value pair for the CamelContext
]]>
</xs:documentation>
</xs:annotation>
@@ -659,8 +603,7 @@ Models a string key/value pair for configuring some global options on a Camel co
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Models a series of string key/value pairs for configuring some global options on a Camel context such as max debug log
-length.
+Defines a collection of global configuration options for the CamelContext
]]>
</xs:documentation>
</xs:annotation>
@@ -669,7 +612,7 @@ length.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Unmarshal unstructured data to objects using Logstash based Grok patterns.
+Unmarshal unstructured data to objects using Logstash based Grok patterns
]]>
</xs:documentation>
</xs:annotation>
@@ -678,52 +621,52 @@ Unmarshal unstructured data to objects using Logstash based Grok patterns.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a Groovy script.
+Evaluates a Groovy script
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
- <xs:element name="groovyXml" type="tns:groovyXmlDataFormat">
+ <xs:element name="groovyJson" type="tns:groovyJSonDataFormat">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Transform between XML and Groovy Node (Map structure) objects.
+Transform between JSon and java.util.Map or java.util.List objects
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
- <xs:element name="gzipDeflater" type="tns:gzipDeflaterDataFormat">
+ <xs:element name="groovyXml" type="tns:groovyXmlDataFormat">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Compress and decompress messages using java.util.zip.GZIPStream.
+Transform between XML and Groovy Node (Map structure) objects
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
- <xs:element name="head" type="tns:headDefinition">
+ <xs:element name="gzipDeflater" type="tns:gzipDeflaterDataFormat">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest HEAD command
+Compress and decompress messages using java.util.zip.GZIP*Stream
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
- <xs:element name="header" type="tns:headerExpression">
+ <xs:element name="head" type="tns:headDefinition">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Gets a header from the Exchange.
+Defines an HTTP HEAD operation in the REST DSL
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
- <xs:element name="healthyServiceFilter" type="tns:healthyServiceCallServiceFilterConfiguration">
+ <xs:element name="header" type="tns:headerExpression">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Deprecated: null
+Gets a header from the Exchange
]]>
</xs:documentation>
</xs:annotation>
@@ -732,7 +675,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal HL7 (Health Care) model objects using the HL7 MLLP codec.
+Marshal and unmarshal HL7 (Health Care) model objects using the HL7 MLLP codec
]]>
</xs:documentation>
</xs:annotation>
@@ -741,7 +684,7 @@ Marshal and unmarshal HL7 (Health Care) model objects using the HL7 MLLP codec.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Get the value of a HL7 message field specified by terse location specification syntax.
+Get the value of a HL7 message field specified by terse location specification syntax
]]>
</xs:documentation>
</xs:annotation>
@@ -750,7 +693,7 @@ Get the value of a HL7 message field specified by terse location specification s
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal iCal (.ics) documents to/from model objects.
+Marshal and unmarshal iCal (*.ics) documents to/from model objects
]]>
</xs:documentation>
</xs:annotation>
@@ -759,7 +702,8 @@ Marshal and unmarshal iCal (.ics) documents to/from model objects.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Filters out duplicate messages
+Filters out duplicate messages based on a unique message identifier and an idempotent repository that tracks previously
+seen IDs
]]>
</xs:documentation>
</xs:annotation>
@@ -768,12 +712,8 @@ Filters out duplicate messages
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set the expected data type of the input message. If the actual message type is different at runtime, camel look for a
-required Transformer and apply if exists. If validate attribute is true then camel applies Validator as well. Type name
-consists of two parts, 'scheme' and 'name' connected with ':'. For Java type 'name' is a fully qualified class name. For
-example {code java:java.lang.String} , {code json:ABCOrder} . It's also possible to specify only scheme part, so that it
-works like a wildcard. If only 'xml' is specified, all the XML message matches. It's handy to add only one
-transformer/validator for all the transformation from/to XML.
+Declares the expected input data type for a route. Camel will apply a data type transformer if the actual message type
+differs at runtime.
]]>
</xs:documentation>
</xs:annotation>
@@ -782,7 +722,7 @@ transformer/validator for all the transformation from/to XML.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Intercepts a message at each step in the route
+Intercepts each message at every processing step in the route, allowing cross-cutting logic such as logging or auditing
]]>
</xs:documentation>
</xs:annotation>
@@ -791,7 +731,7 @@ Intercepts a message at each step in the route
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Intercepts incoming messages
+Intercepts incoming messages arriving from consumer endpoints, optionally filtering by endpoint URI pattern
]]>
</xs:documentation>
</xs:annotation>
@@ -800,7 +740,7 @@ Intercepts incoming messages
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Intercepts messages being sent to an endpoint
+Intercepts messages being sent to a specific endpoint, allowing the message to be modified or the send to be skipped
]]>
</xs:documentation>
</xs:annotation>
@@ -809,7 +749,7 @@ Intercepts messages being sent to an endpoint
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Create, edit and read ISO-8583 messages.
+Create, edit and read ISO-8583 messages
]]>
</xs:documentation>
</xs:annotation>
@@ -818,7 +758,16 @@ Create, edit and read ISO-8583 messages.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Unmarshal an XML payloads to POJOs and back using XMLMapper extension of Jackson.
+Unmarshal an XML payloads to POJOs and back using XMLMapper extension of Jackson
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element name="jactl" type="tns:jactlExpression">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Evaluates a Jactl script
]]>
</xs:documentation>
</xs:annotation>
@@ -827,7 +776,7 @@ Unmarshal an XML payloads to POJOs and back using XMLMapper extension of Jackson
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a Java (Java compiled once at runtime) expression.
+Evaluates a Java (Java compiled once at runtime) expression
]]>
</xs:documentation>
</xs:annotation>
@@ -836,7 +785,7 @@ Evaluates a Java (Java compiled once at runtime) expression.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Unmarshal XML payloads to POJOs and back using JAXB2 XML marshalling standard.
+Unmarshal XML payloads to POJOs and back using JAXB2 XML marshalling standard
]]>
</xs:documentation>
</xs:annotation>
@@ -854,7 +803,7 @@ JMX configuration.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Deprecated: Evaluates a jOOR (Java compiled once at runtime) expression.
+Deprecated: Evaluates a jOOR (Java compiled once at runtime) expression
]]>
</xs:documentation>
</xs:annotation>
@@ -863,7 +812,7 @@ Deprecated: Evaluates a jOOR (Java compiled once at runtime) expression.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a JQ expression against a JSON message body.
+Evaluates a JQ expression against a JSON message body
]]>
</xs:documentation>
</xs:annotation>
@@ -872,7 +821,7 @@ Evaluates a JQ expression against a JSON message body.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a JavaScript expression.
+Evaluates a JavaScript expression
]]>
</xs:documentation>
</xs:annotation>
@@ -881,7 +830,7 @@ Evaluates a JavaScript expression.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal POJOs to JSON and back.
+Marshal POJOs to JSON and back
]]>
</xs:documentation>
</xs:annotation>
@@ -890,7 +839,7 @@ Marshal POJOs to JSON and back.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal JSON:API resources using JSONAPI-Converter library.
+Marshal and unmarshal JSON:API resources using JSONAPI-Converter library
]]>
</xs:documentation>
</xs:annotation>
@@ -899,7 +848,7 @@ Marshal and unmarshal JSON:API resources using JSONAPI-Converter library.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a JSONPath expression against a JSON message body.
+Evaluates a JSONPath expression against a JSON message body
]]>
</xs:documentation>
</xs:annotation>
@@ -908,7 +857,7 @@ Evaluates a JSONPath expression against a JSON message body.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-JTA based transactional error handler (requires camel-jta).
+Transactional error handler using JTA (Java Transaction API) that marks the transaction for rollback on failure
]]>
</xs:documentation>
</xs:annotation>
@@ -917,11 +866,8 @@ JTA based transactional error handler (requires camel-jta).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To call Kamelets in special situations. By default, calling kamelets should be done as endpoints with the kamelet
-component, such as to(kamelet:mykamelet). When a Kamelet is designed for a special use-case such as aggregating
-messages, and returning a response message only when a group of aggregated messages is completed. In other words,
-kamelet does not return a response message for every incoming message. In special situations like these, then you must
-use this Kamelet EIP instead of using the kamelet component.
+Calls a Kamelet (reusable route template) as a step in the route. Normally Kamelets are invoked via kamelet: endpoint
+URIs; this EIP is for special cases where direct invocation is needed.
]]>
</xs:documentation>
</xs:annotation>
@@ -931,15 +877,6 @@ use this Kamelet EIP instead of using the kamelet component.
<xs:documentation xml:lang="en">
<![CDATA[
Key store facility for cryptographic keys and certificates
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="kubernetesServiceDiscovery" type="tns:kubernetesServiceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
]]>
</xs:documentation>
</xs:annotation>
@@ -948,7 +885,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Camel AI: Tokenizer for splitting by character.
+Splits text into chunks by character count, using LangChain4j's character tokenizer for AI text processing
]]>
</xs:documentation>
</xs:annotation>
@@ -957,7 +894,7 @@ Camel AI: Tokenizer for splitting by character.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Camel AI: Tokenizer for splitting line by line.
+Splits text into chunks line by line, using LangChain4j's line tokenizer for AI text processing
]]>
</xs:documentation>
</xs:annotation>
@@ -966,7 +903,7 @@ Camel AI: Tokenizer for splitting line by line.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Camel AI: Tokenizer for splitting by paragraphs.
+Splits text into chunks by paragraph boundaries, using LangChain4j's paragraph tokenizer for AI text processing
]]>
</xs:documentation>
</xs:annotation>
@@ -975,7 +912,7 @@ Camel AI: Tokenizer for splitting by paragraphs.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Camel AI: Tokenizer for splitting by sentences.
+Splits text into chunks by sentence boundaries, using LangChain4j's sentence tokenizer for AI text processing
]]>
</xs:documentation>
</xs:annotation>
@@ -984,7 +921,7 @@ Camel AI: Tokenizer for splitting by sentences.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Camel AI: Tokenizer for splitting by word.
+Splits text into chunks by word boundaries, using LangChain4j's word tokenizer for AI text processing
]]>
</xs:documentation>
</xs:annotation>
@@ -993,7 +930,7 @@ Camel AI: Tokenizer for splitting by word.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a custom language.
+Evaluates a custom language
]]>
</xs:documentation>
</xs:annotation>
@@ -1002,16 +939,8 @@ Evaluates a custom language.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Balances message processing among a number of nodes
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="loadBalancerConfiguration" type="tns:serviceCallServiceLoadBalancerConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+Distributes messages across multiple endpoints using a load balancing strategy such as round-robin, random, failover, or
+weighted
]]>
</xs:documentation>
</xs:annotation>
@@ -1020,7 +949,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To load custom transformers from classpath scanning to be used for route level transformations.
+Auto-discovers and loads data type transformers from the classpath via scanning
]]>
</xs:documentation>
</xs:annotation>
@@ -1029,7 +958,7 @@ To load custom transformers from classpath scanning to be used for route level t
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Used for printing custom messages to the logger.
+Logs a message using an expression that can include message body, headers, and other exchange data
]]>
</xs:documentation>
</xs:annotation>
@@ -1038,7 +967,7 @@ Used for printing custom messages to the logger.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Processes a message multiple times
+Processes the message body repeatedly for a specified number of iterations, or until a condition is met
]]>
</xs:documentation>
</xs:annotation>
@@ -1047,7 +976,7 @@ Processes a message multiple times
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Compress and decompress streams using LZF deflate algorithm.
+Compress and decompress streams using LZF deflate algorithm
]]>
</xs:documentation>
</xs:annotation>
@@ -1056,7 +985,7 @@ Compress and decompress streams using LZF deflate algorithm.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshals data into a specified format for transmission over a transport or component
+Serializes the message body into a specific data format such as JSON, XML, CSV, or Protobuf for transmission or storage
]]>
</xs:documentation>
</xs:annotation>
@@ -1065,7 +994,7 @@ Marshals data into a specified format for transmission over a transport or compo
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Calls a Java bean method.
+Calls a Java bean method
]]>
</xs:documentation>
</xs:annotation>
@@ -1074,7 +1003,7 @@ Calls a Java bean method.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal Camel messages with attachments into MIME-Multipart messages and back.
+Marshal Camel messages with attachments into MIME-Multipart messages and back
]]>
</xs:documentation>
</xs:annotation>
@@ -1083,7 +1012,8 @@ Marshal Camel messages with attachments into MIME-Multipart messages and back.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Routes the same message to multiple paths either sequentially or in parallel.
+Sends a copy of the message to multiple fixed endpoints, processing them sequentially or in parallel, and optionally
+aggregating their replies
]]>
</xs:documentation>
</xs:annotation>
@@ -1092,7 +1022,7 @@ Routes the same message to multiple paths either sequentially or in parallel.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest security mutual TLS authentication definition
+Configures mutual TLS (mTLS) client certificate authentication for a REST service
]]>
</xs:documentation>
</xs:annotation>
@@ -1101,7 +1031,7 @@ Rest security mutual TLS authentication definition
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a MVEL template.
+Evaluates a MVEL template
]]>
</xs:documentation>
</xs:annotation>
@@ -1110,7 +1040,7 @@ Evaluates a MVEL template.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To not use an error handler.
+Disables error handling for a route, causing exceptions to propagate immediately to the caller
]]>
</xs:documentation>
</xs:annotation>
@@ -1119,7 +1049,7 @@ To not use an error handler.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest security OAuth2 definition
+Configures OAuth2 authentication for a REST service
]]>
</xs:documentation>
</xs:annotation>
@@ -1128,7 +1058,7 @@ Rest security OAuth2 definition
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal OCSF (Open Cybersecurity Schema Framework) security events to/from JSON.
+Marshal and unmarshal OCSF (Open Cybersecurity Schema Framework) security events to/from JSON
]]>
</xs:documentation>
</xs:annotation>
@@ -1137,7 +1067,7 @@ Marshal and unmarshal OCSF (Open Cybersecurity Schema Framework) security events
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Deprecated: Evaluates an OGNL expression (Apache Commons OGNL).
+Deprecated: Evaluates an OGNL expression (Apache Commons OGNL)
]]>
</xs:documentation>
</xs:annotation>
@@ -1146,7 +1076,7 @@ Deprecated: Evaluates an OGNL expression (Apache Commons OGNL).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route to be executed when normal route processing completes
+Defines steps to execute when route processing completes, either on success, failure, or both
]]>
</xs:documentation>
</xs:annotation>
@@ -1155,7 +1085,8 @@ Route to be executed when normal route processing completes
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route to be executed when an exception is thrown
+Defines exception handling for specific exception types, with options for redelivery, logging, and routing to error
+endpoints
]]>
</xs:documentation>
</xs:annotation>
@@ -1164,7 +1095,7 @@ Route to be executed when an exception is thrown
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route to be executed when Circuit Breaker EIP executes fallback
+Defines the fallback route that executes when the Circuit Breaker trips or the primary route fails
]]>
</xs:documentation>
</xs:annotation>
@@ -1173,7 +1104,8 @@ Route to be executed when Circuit Breaker EIP executes fallback
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a predicate to determine when to trigger this.
+Applies a predicate condition to filter when a parent definition (such as onException or onCompletion) should be
+triggered
]]>
</xs:documentation>
</xs:annotation>
@@ -1182,7 +1114,8 @@ To use a predicate to determine when to trigger this.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use OpenApi as contract-first with Camel Rest DSL.
+Configures a contract-first REST service using an OpenAPI specification, where Camel auto-generates routes for each
+operation
]]>
</xs:documentation>
</xs:annotation>
@@ -1191,7 +1124,7 @@ To use OpenApi as contract-first with Camel Rest DSL.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest security OpenID Connect definition
+Configures OpenID Connect authentication for a REST service
]]>
</xs:documentation>
</xs:annotation>
@@ -1200,7 +1133,8 @@ Rest security OpenID Connect definition
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure optimistic locking
+Configures the retry policy for optimistic locking in the Aggregate EIP, controlling retry attempts and delays on
+version conflicts
]]>
</xs:documentation>
</xs:annotation>
@@ -1209,7 +1143,7 @@ To configure optimistic locking
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route to be executed when all other choices evaluate to false
+Defines the default branch within a Choice EIP that executes when no When condition matches
]]>
</xs:documentation>
</xs:annotation>
@@ -1218,12 +1152,8 @@ Route to be executed when all other choices evaluate to false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set the expected data type of the output message. If the actual message type is different at runtime, camel look for a
-required Transformer and apply if exists. If validate attribute is true then camel applies Validator as well. Type name
-consists of two parts, 'scheme' and 'name' connected with ':'. For Java type 'name' is a fully qualified class name. For
-example {code java:java.lang.String} , {code json:ABCOrder} . It's also possible to specify only scheme part, so that it
-works like a wildcard. If only 'xml' is specified, all the XML message matches. It's handy to add only one
-transformer/validator for all the XML-Java transformation.
+Declares the expected output data type for a route. Camel will apply a data type transformer if the actual message type
+differs at runtime.
]]>
</xs:documentation>
</xs:annotation>
@@ -1232,7 +1162,7 @@ transformer/validator for all the XML-Java transformation.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Scans for Java org.apache.camel.builder.RouteBuilder classes in java packages
+Scans Java packages on the classpath for RouteBuilder classes to auto-discover and register routes
]]>
</xs:documentation>
</xs:annotation>
@@ -1241,7 +1171,7 @@ Scans for Java org.apache.camel.builder.RouteBuilder classes in java packages
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To specify the rest operation parameters.
+Defines a parameter for a REST operation, specifying its type, name, data type, and whether it is required
]]>
</xs:documentation>
</xs:annotation>
@@ -1250,16 +1180,7 @@ To specify the rest operation parameters.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Parquet Avro serialization and de-serialization.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="passThroughServiceFilter" type="tns:passThroughServiceCallServiceFilterConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+Parquet Avro serialization and de-serialization
]]>
</xs:documentation>
</xs:annotation>
@@ -1268,7 +1189,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest PATCH command
+Defines an HTTP PATCH operation in the REST DSL
]]>
</xs:documentation>
</xs:annotation>
@@ -1277,7 +1198,8 @@ Rest PATCH command
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Pausable EIP to support resuming processing from last known offset.
+Pauses a consumer based on a condition, allowing it to be resumed later from the last known offset. Useful for
+controlling ingestion rate on polling consumers.
]]>
</xs:documentation>
</xs:annotation>
@@ -1286,7 +1208,7 @@ Pausable EIP to support resuming processing from last known offset.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encrypt and decrypt messages using Java Cryptographic Extension (JCE) and PGP.
+Encrypt and decrypt messages using Java Cryptographic Extension (JCE) and PGP
]]>
</xs:documentation>
</xs:annotation>
@@ -1295,7 +1217,7 @@ Encrypt and decrypt messages using Java Cryptographic Extension (JCE) and PGP.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Routes the message to a sequence of processors.
+Processes the message through a sequence of steps where the output of each step becomes the input of the next
]]>
</xs:documentation>
</xs:annotation>
@@ -1304,7 +1226,7 @@ Routes the message to a sequence of processors.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines a policy the route will use
+Applies a policy to the route, such as a transactional policy or a custom policy for cross-cutting concerns
]]>
</xs:documentation>
</xs:annotation>
@@ -1313,7 +1235,8 @@ Defines a policy the route will use
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Polls a message from a static endpoint
+Polls a single message from a consumer endpoint and sets it as the message body. Useful for fetching data on-demand from
+file, database, or messaging endpoints.
]]>
</xs:documentation>
</xs:annotation>
@@ -1322,7 +1245,8 @@ Polls a message from a static endpoint
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Enriches messages with data polled from a secondary resource
+Enriches the message with additional data obtained by polling a consumer endpoint (such as a file or message queue). The
+polled data is merged using an aggregation strategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -1331,7 +1255,7 @@ Enriches messages with data polled from a secondary resource
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest POST command
+Defines an HTTP POST operation in the REST DSL
]]>
</xs:documentation>
</xs:annotation>
@@ -1340,7 +1264,7 @@ Rest POST command
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encrypt and decrypt messages using Post-Quantum Cryptography Key Encapsulation Mechanisms (KEM).
+Encrypt and decrypt messages using Post-Quantum Cryptography Key Encapsulation Mechanisms (KEM)
]]>
</xs:documentation>
</xs:annotation>
@@ -1349,7 +1273,7 @@ Encrypt and decrypt messages using Post-Quantum Cryptography Key Encapsulation M
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a predicate to perform validation on the route level.
+Uses a predicate expression to validate message data types at the route level
]]>
</xs:documentation>
</xs:annotation>
@@ -1358,7 +1282,7 @@ To use a predicate to perform validation on the route level.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Calls a Camel processor
+Invokes a custom Camel Processor for programmatic message processing in Java
]]>
</xs:documentation>
</xs:annotation>
@@ -1385,7 +1309,7 @@ Properties to use with properties placeholder
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A key value pair where the value is a literal value
+Defines a key/value pair with a literal value, used for passing parameters in route templates and other configurations
]]>
</xs:documentation>
</xs:annotation>
@@ -1394,7 +1318,7 @@ A key value pair where the value is a literal value
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A key value pair where the value is an expression.
+Defines a key/value pair where the value is computed by an expression, used for passing dynamic parameters
]]>
</xs:documentation>
</xs:annotation>
@@ -1412,7 +1336,7 @@ Properties placeholder
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Serialize and deserialize Java objects using Google's Protocol buffers.
+Serialize and deserialize Java objects using Google's Protocol buffers
]]>
</xs:documentation>
</xs:annotation>
@@ -1421,7 +1345,7 @@ Serialize and deserialize Java objects using Google's Protocol buffers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest PUT command
+Defines an HTTP PUT operation in the REST DSL
]]>
</xs:documentation>
</xs:annotation>
@@ -1430,7 +1354,7 @@ Rest PUT command
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a Python expression.
+Evaluates a Python expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1439,7 +1363,7 @@ Evaluates a Python expression.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The destination endpoints are selected randomly.
+Load balancer that randomly selects a destination endpoint for each message
]]>
</xs:documentation>
</xs:annotation>
@@ -1448,7 +1372,8 @@ The destination endpoints are selected randomly.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Route messages to a number of dynamically specified recipients
+Routes a message to a list of dynamically calculated endpoints, determined at runtime from an expression. Each recipient
+receives a copy of the message.
]]>
</xs:documentation>
</xs:annotation>
@@ -1457,7 +1382,7 @@ Route messages to a number of dynamically specified recipients
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure re-delivery for error handling
+Configures message redelivery for error handling, including maximum retries, delay patterns, and backoff settings
]]>
</xs:documentation>
</xs:annotation>
@@ -1475,7 +1400,7 @@ Configuration of redelivery policy.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Uses an existing expression from the registry.
+Uses an existing expression from the registry
]]>
</xs:documentation>
</xs:annotation>
@@ -1484,7 +1409,7 @@ Uses an existing expression from the registry.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-References to an existing or custom error handler.
+References a custom error handler bean from the registry by its name
]]>
</xs:documentation>
</xs:annotation>
@@ -1493,7 +1418,7 @@ References to an existing or custom error handler.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Removes a named header from the message
+Removes a specific header from the message by name
]]>
</xs:documentation>
</xs:annotation>
@@ -1502,7 +1427,8 @@ Removes a named header from the message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Removes message headers whose name matches a specified pattern
+Removes all message headers whose names match a given pattern. Useful for stripping internal Camel headers before
+sending to external systems.
]]>
</xs:documentation>
</xs:annotation>
@@ -1511,7 +1437,7 @@ Removes message headers whose name matches a specified pattern
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Removes message exchange properties whose name matches a specified pattern
+Removes all exchange properties whose names match a given pattern
]]>
</xs:documentation>
</xs:annotation>
@@ -1520,7 +1446,7 @@ Removes message exchange properties whose name matches a specified pattern
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Removes a named property from the message exchange
+Removes a specific exchange property by name
]]>
</xs:documentation>
</xs:annotation>
@@ -1529,7 +1455,7 @@ Removes a named property from the message exchange
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Removes a named variable
+Removes a specific variable by name
]]>
</xs:documentation>
</xs:annotation>
@@ -1538,7 +1464,8 @@ Removes a named variable
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Resequences (re-order) messages based on an expression
+Reorders messages based on a sequence expression, either in batch mode (collect and sort) or stream mode (continuous
+reordering with a timeout)
]]>
</xs:documentation>
</xs:annotation>
@@ -1547,7 +1474,8 @@ Resequences (re-order) messages based on an expression
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Resilience4j Circuit Breaker EIP configuration
+Configures Resilience4j settings for the Circuit Breaker EIP, such as failure rate threshold, wait duration, and sliding
+window parameters
]]>
</xs:documentation>
</xs:annotation>
@@ -1556,7 +1484,7 @@ Resilience4j Circuit Breaker EIP configuration
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To specify the rest operation response headers.
+Defines a response header for a REST operation, used for API documentation and OpenAPI spec generation
]]>
</xs:documentation>
</xs:annotation>
@@ -1565,7 +1493,7 @@ To specify the rest operation response headers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To specify the rest operation response messages.
+Defines a response message for a REST operation, including HTTP status code and description for API documentation
]]>
</xs:documentation>
</xs:annotation>
@@ -1574,7 +1502,7 @@ To specify the rest operation response messages.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines a rest service using the rest-dsl
+Defines a REST service with HTTP operations (GET, POST, PUT, DELETE, etc.) using the Camel REST DSL
]]>
</xs:documentation>
</xs:annotation>
@@ -1583,7 +1511,7 @@ Defines a rest service using the rest-dsl
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure rest binding
+Configures data binding for a REST service, controlling how request and response bodies are marshalled and unmarshalled
]]>
</xs:documentation>
</xs:annotation>
@@ -1592,7 +1520,8 @@ To configure rest binding
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure rest
+Configures global settings for the REST DSL, such as host, port, context path, binding mode, and the underlying HTTP
+component to use
]]>
</xs:documentation>
</xs:annotation>
@@ -1610,7 +1539,7 @@ Configuration of REST services using rest-dsl using XML
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To refer to an XML file with rest services defined using the rest-dsl
+References an external XML file containing REST service definitions for inclusion in the current context
]]>
</xs:documentation>
</xs:annotation>
@@ -1619,7 +1548,7 @@ To refer to an XML file with rest services defined using the rest-dsl
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A key value pair
+Defines a key/value property for REST configuration, used to pass component-specific settings
]]>
</xs:documentation>
</xs:annotation>
@@ -1628,7 +1557,7 @@ A key value pair
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A series of rest services defined using the rest-dsl
+Container for a collection of REST service definitions
]]>
</xs:documentation>
</xs:annotation>
@@ -1637,7 +1566,8 @@ A series of rest services defined using the rest-dsl
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Resume EIP to support resuming processing from last known offset.
+Enables resuming processing from the last known offset after a restart, using a resume strategy to track and restore
+position
]]>
</xs:documentation>
</xs:annotation>
@@ -1646,7 +1576,7 @@ Resume EIP to support resuming processing from last known offset.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Forces a rollback by stopping routing the message
+Forces a rollback of the current transaction and stops routing the message. Can set a custom message on the exception.
]]>
</xs:documentation>
</xs:annotation>
@@ -1655,8 +1585,7 @@ Forces a rollback by stopping routing the message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The destination endpoints are selected in a round-robin fashion. This is a well-known and classic policy, which spreads
-the load evenly.
+Load balancer that cycles through destination endpoints in sequential order, distributing the load evenly
]]>
</xs:documentation>
</xs:annotation>
@@ -1665,7 +1594,8 @@ the load evenly.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A Camel route
+Defines a Camel route that specifies the processing steps a message goes through from a consumer endpoint to one or more
+producer endpoints
]]>
</xs:documentation>
</xs:annotation>
@@ -1674,7 +1604,7 @@ A Camel route
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To refer to a Java org.apache.camel.builder.RouteBuilder instance to use.
+References a Java RouteBuilder class to include its routes in the current CamelContext
]]>
</xs:documentation>
</xs:annotation>
@@ -1683,7 +1613,8 @@ To refer to a Java org.apache.camel.builder.RouteBuilder instance to use.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reusable configuration for Camel route(s).
+Defines reusable configuration that is automatically applied to matching routes, such as shared error handling or
+interceptors
]]>
</xs:documentation>
</xs:annotation>
@@ -1701,7 +1632,7 @@ Configuration of route configurations using XML
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To refer to an XML file with route configuration defined using the xml-dsl
+References an external XML file containing route configuration definitions for inclusion in the current context
]]>
</xs:documentation>
</xs:annotation>
@@ -1710,7 +1641,7 @@ To refer to an XML file with route configuration defined using the xml-dsl
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A series of route configurations
+Container for a collection of route configuration definitions
]]>
</xs:documentation>
</xs:annotation>
@@ -1728,7 +1659,7 @@ Configuration of routes using XML
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To refer to an XML file with routes defined using the xml-dsl
+References an external XML file containing route definitions for inclusion in the current context
]]>
</xs:documentation>
</xs:annotation>
@@ -1746,7 +1677,7 @@ Route controller configuration.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines a route template (parameterized routes)
+Defines a parameterized route template that can be instantiated multiple times with different parameter values
]]>
</xs:documentation>
</xs:annotation>
@@ -1764,7 +1695,7 @@ Configuration of route templates using XML
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To refer to an XML file with route templates defined using the xml-dsl
+References an external XML file containing route template definitions for inclusion in the current context
]]>
</xs:documentation>
</xs:annotation>
@@ -1773,7 +1704,7 @@ To refer to an XML file with route templates defined using the xml-dsl
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A series of route templates
+Container for a collection of route template definitions
]]>
</xs:documentation>
</xs:annotation>
@@ -1782,7 +1713,7 @@ A series of route templates
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A series of Camel routes
+Container for a collection of route definitions
]]>
</xs:documentation>
</xs:annotation>
@@ -1791,7 +1722,8 @@ A series of Camel routes
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Routes a message through a series of steps that are pre-determined (the slip)
+Routes a message through a pre-determined sequence of endpoints defined in a header or expression (the routing slip).
+The list of endpoints is evaluated once upfront.
]]>
</xs:documentation>
</xs:annotation>
@@ -1800,7 +1732,7 @@ Routes a message through a series of steps that are pre-determined (the slip)
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Transform from ROME SyndFeed Java Objects to XML and vice-versa.
+Transform from ROME SyndFeed Java Objects to XML and vice-versa
]]>
</xs:documentation>
</xs:annotation>
@@ -1809,7 +1741,8 @@ Transform from ROME SyndFeed Java Objects to XML and vice-versa.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Enables Sagas on the route
+Defines a Saga (long-running action) that coordinates distributed services toward a consistent outcome. Unlike XA
+transactions, Sagas use compensating actions for rollback and work across heterogeneous services.
]]>
</xs:documentation>
</xs:annotation>
@@ -1818,7 +1751,8 @@ Enables Sagas on the route
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Extract a sample of the messages passing through a route
+Samples a subset of messages passing through the route, either by frequency count or time interval, and discards the
+rest
]]>
</xs:documentation>
</xs:annotation>
@@ -1827,7 +1761,7 @@ Extract a sample of the messages passing through a route
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Executes a script from a language which does not change the message body.
+Executes an expression or script in a chosen language for side effects without modifying the message body
]]>
</xs:documentation>
</xs:annotation>
@@ -1845,7 +1779,7 @@ Cryptographically strong random number generator
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Rest security definition
+Applies a security requirement to a REST operation, referencing a security scheme defined at the service level
]]>
</xs:documentation>
</xs:annotation>
@@ -1854,61 +1788,7 @@ Rest security definition
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure rest security definitions.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="serviceCall" type="tns:serviceCallDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: To call remote services
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="serviceCallConfiguration" type="tns:serviceCallConfigurationDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: Remote service call configuration
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="serviceChooserConfiguration" type="tns:serviceCallServiceChooserConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="serviceDiscoveryConfiguration" type="tns:serviceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="serviceExpression" type="tns:serviceCallExpressionConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="serviceFilterConfiguration" type="tns:serviceCallServiceFilterConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+Container for security scheme definitions used by REST services
]]>
</xs:documentation>
</xs:annotation>
@@ -1917,7 +1797,7 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the contents of the message body
+Sets the message body to a value computed by an expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1926,7 +1806,7 @@ Sets the contents of the message body
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the exchange pattern on the message exchange
+Sets the message exchange pattern (MEP) on the exchange, such as InOnly for one-way or InOut for request-reply
]]>
</xs:documentation>
</xs:annotation>
@@ -1935,7 +1815,7 @@ Sets the exchange pattern on the message exchange
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the value of a message header
+Sets a message header to a value computed by an expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1944,7 +1824,7 @@ Sets the value of a message header
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Allows setting multiple headers on the message at the same time.
+Sets multiple message headers at once, each computed by its own expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1953,7 +1833,7 @@ Allows setting multiple headers on the message at the same time.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a named property on the message exchange
+Sets an exchange property to a value computed by an expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1962,7 +1842,7 @@ Sets a named property on the message exchange
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the value of a variable
+Sets a variable to a value computed by an expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1971,7 +1851,7 @@ Sets the value of a variable
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Allows setting multiple variables at the same time.
+Sets multiple variables at once, each computed by its own expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1980,7 +1860,7 @@ Allows setting multiple variables at the same time.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a Camel simple expression.
+Evaluates a Camel simple expression
]]>
</xs:documentation>
</xs:annotation>
@@ -1989,7 +1869,7 @@ Evaluates a Camel simple expression.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Transform and bind XML as well as non-XML data, including EDI, CSV, JSON, and YAML using Smooks.
+Transform and bind XML as well as non-XML data, including EDI, CSV, JSON, and YAML using Smooks
]]>
</xs:documentation>
</xs:annotation>
@@ -1998,7 +1878,7 @@ Transform and bind XML as well as non-XML data, including EDI, CSV, JSON, and YA
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal Java objects to SOAP messages and back.
+Marshal Java objects to SOAP messages and back
]]>
</xs:documentation>
</xs:annotation>
@@ -2007,7 +1887,7 @@ Marshal Java objects to SOAP messages and back.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sorts the contents of the message
+Sorts the items in a message body that is a List, using a specified comparator or the default ordering
]]>
</xs:documentation>
</xs:annotation>
@@ -2016,7 +1896,7 @@ Sorts the contents of the message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates a Spring expression (SpEL).
+Evaluates a Spring expression (SpEL)
]]>
</xs:documentation>
</xs:annotation>
@@ -2025,7 +1905,8 @@ Evaluates a Spring expression (SpEL).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Splits a single message into many sub-messages.
+Splits a message into multiple sub-messages using an expression, and processes each one individually. Supports parallel
+processing and result aggregation.
]]>
</xs:documentation>
</xs:annotation>
@@ -2034,7 +1915,7 @@ Splits a single message into many sub-messages.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Spring based transactional error handler (requires camel-spring).
+Transactional error handler using Spring Transaction Manager that marks the transaction for rollback on failure
]]>
</xs:documentation>
</xs:annotation>
@@ -2044,15 +1925,6 @@ Spring based transactional error handler (requires camel-spring).
<xs:documentation xml:lang="en">
<![CDATA[
Secure socket protocol configuration
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="staticServiceDiscovery" type="tns:staticServiceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
]]>
</xs:documentation>
</xs:annotation>
@@ -2061,7 +1933,8 @@ Deprecated: null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Routes the message to a sequence of processors which is grouped together as one logical name
+Groups a sequence of processing steps under a single logical name for improved monitoring, management, and tracing
+visibility
]]>
</xs:documentation>
</xs:annotation>
@@ -2070,7 +1943,7 @@ Routes the message to a sequence of processors which is grouped together as one
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sticky load balancing using an expression to calculate a correlation key to perform the sticky load balancing.
+Load balancer that routes messages to the same endpoint based on a correlation expression, ensuring session affinity
]]>
</xs:documentation>
</xs:annotation>
@@ -2079,7 +1952,7 @@ Sticky load balancing using an expression to calculate a correlation key to perf
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Stops the processing of the current message
+Stops processing of the current message and marks the exchange as completed without sending it to any further steps
]]>
</xs:documentation>
</xs:annotation>
@@ -2097,7 +1970,8 @@ Stream caching configuration.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Configures stream-processing resequence eip.
+Configures the stream-processing mode of the Resequence EIP, which continuously reorders messages as they arrive using a
+timeout
]]>
</xs:documentation>
</xs:annotation>
@@ -2106,7 +1980,7 @@ Configures stream-processing resequence eip.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encode and decode SWIFT MT messages.
+Encode and decode SWIFT MT messages
]]>
</xs:documentation>
</xs:annotation>
@@ -2115,7 +1989,7 @@ Encode and decode SWIFT MT messages.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encode and decode SWIFT MX messages.
+Encode and decode SWIFT MX messages
]]>
</xs:documentation>
</xs:annotation>
@@ -2124,7 +1998,7 @@ Encode and decode SWIFT MX messages.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshall SyslogMessages to RFC3164 and RFC5424 messages and back.
+Marshall SyslogMessages to RFC3164 and RFC5424 messages and back
]]>
</xs:documentation>
</xs:annotation>
@@ -2133,7 +2007,7 @@ Marshall SyslogMessages to RFC3164 and RFC5424 messages and back.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Archive files into tarballs or extract files from tarballs.
+Archive files into tarballs or extract files from tarballs
]]>
</xs:documentation>
</xs:annotation>
@@ -2151,7 +2025,7 @@ Configures a ProducerTemplate
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A route template parameter
+Defines a parameter for a route template, with an optional default value and description
]]>
</xs:documentation>
</xs:annotation>
@@ -2160,7 +2034,7 @@ A route template parameter
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines a templated route (a route built from a route template)
+Creates a route instance from a route template, binding specific parameter values to the template's parameters
]]>
</xs:documentation>
</xs:annotation>
@@ -2169,7 +2043,7 @@ Defines a templated route (a route built from a route template)
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-An input parameter of a route template.
+Provides a parameter value for a templated route, binding a value to a route template parameter
]]>
</xs:documentation>
</xs:annotation>
@@ -2178,7 +2052,7 @@ An input parameter of a route template.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A series of templated routes
+Container for a collection of templated route definitions
]]>
</xs:documentation>
</xs:annotation>
@@ -2196,7 +2070,8 @@ Configuration of thread pools
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure thread pools
+Defines a named thread pool profile with pool size, queue size, and thread keep-alive settings for use by EIPs and
+components
]]>
</xs:documentation>
</xs:annotation>
@@ -2205,7 +2080,8 @@ To configure thread pools
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Specifies that all steps after this node are processed asynchronously
+Offloads processing of subsequent steps in the route to a thread pool, enabling asynchronous and concurrent message
+handling
]]>
</xs:documentation>
</xs:annotation>
@@ -2214,7 +2090,7 @@ Specifies that all steps after this node are processed asynchronously
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Serialize and deserialize messages using Apache Thrift binary data format.
+Serialize and deserialize messages using Apache Thrift binary data format
]]>
</xs:documentation>
</xs:annotation>
@@ -2223,7 +2099,7 @@ Serialize and deserialize messages using Apache Thrift binary data format.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Controls the rate at which messages are passed to the next node in the route
+Limits the message throughput to a maximum number of messages per time period to avoid overloading downstream systems
]]>
</xs:documentation>
</xs:annotation>
@@ -2232,7 +2108,7 @@ Controls the rate at which messages are passed to the next node in the route
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Throws an exception
+Throws an exception during route processing, either creating a new exception instance or re-throwing an existing one
]]>
</xs:documentation>
</xs:annotation>
@@ -2241,7 +2117,7 @@ Throws an exception
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sends the message to a static endpoint
+Sends the message to a fixed endpoint URI
]]>
</xs:documentation>
</xs:annotation>
@@ -2250,7 +2126,8 @@ Sends the message to a static endpoint
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sends the message to a dynamic endpoint
+Sends the message to an endpoint URI computed dynamically from an expression, allowing the destination to vary per
+message
]]>
</xs:documentation>
</xs:annotation>
@@ -2259,7 +2136,7 @@ Sends the message to a dynamic endpoint
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Tokenize text payloads using delimiter patterns.
+Tokenize text payloads using delimiter patterns
]]>
</xs:documentation>
</xs:annotation>
@@ -2268,7 +2145,7 @@ Tokenize text payloads using delimiter patterns.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Represents a Camel tokenizer for AI.
+Tokenizes the message body for AI processing, splitting text into chunks suitable for embedding or LLM input
]]>
</xs:documentation>
</xs:annotation>
@@ -2277,7 +2154,7 @@ Represents a Camel tokenizer for AI.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Topic which sends to all destinations.
+Load balancer that sends every message to all destination endpoints, similar to a publish-subscribe pattern
]]>
</xs:documentation>
</xs:annotation>
@@ -2286,7 +2163,8 @@ Topic which sends to all destinations.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Enables transaction on the route
+Wraps the route in a transaction, ensuring that all steps within the transacted block either complete together or roll
+back on failure
]]>
</xs:documentation>
</xs:annotation>
@@ -2295,7 +2173,7 @@ Enables transaction on the route
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Transforms the message body based on an expression
+Sets the message body using an expression. Unlike setBody, transform also sets the OUT message body in InOut exchanges
]]>
</xs:documentation>
</xs:annotation>
@@ -2304,7 +2182,8 @@ Transforms the message body based on an expression
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Transforms the message body based on known data type transformers.
+Transforms the message body between known data types (such as XML, JSON, Java objects) using registered data type
+transformers
]]>
</xs:documentation>
</xs:annotation>
@@ -2313,7 +2192,7 @@ Transforms the message body based on known data type transformers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure transformers.
+Container for defining data type transformer definitions
]]>
</xs:documentation>
</xs:annotation>
@@ -2322,7 +2201,7 @@ To configure transformers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal Java objects from and to CSV (Comma Separated Values) using UniVocity Parsers.
+Marshal and unmarshal Java objects from and to CSV (Comma Separated Values) using UniVocity Parsers
]]>
</xs:documentation>
</xs:annotation>
@@ -2331,7 +2210,7 @@ Marshal and unmarshal Java objects from and to CSV (Comma Separated Values) usin
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal Java objects from and to fixed length records using UniVocity Parsers.
+Marshal and unmarshal Java objects from and to fixed length records using UniVocity Parsers
]]>
</xs:documentation>
</xs:annotation>
@@ -2340,7 +2219,7 @@ Marshal and unmarshal Java objects from and to fixed length records using UniVoc
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure headers for UniVocity data formats.
+Defines a column header for UniVocity data format configuration
]]>
</xs:documentation>
</xs:annotation>
@@ -2349,7 +2228,7 @@ To configure headers for UniVocity data formats.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal Java objects from and to TSV (Tab-Separated Values) records using UniVocity Parsers.
+Marshal and unmarshal Java objects from and to TSV (Tab-Separated Values) records using UniVocity Parsers
]]>
</xs:documentation>
</xs:annotation>
@@ -2358,7 +2237,7 @@ Marshal and unmarshal Java objects from and to TSV (Tab-Separated Values) record
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Converts the message data received from the wire into a format that Apache Camel processors can consume
+Deserializes the message body from a specific data format such as JSON, XML, CSV, or Protobuf into a Java object
]]>
</xs:documentation>
</xs:annotation>
@@ -2367,7 +2246,7 @@ Converts the message data received from the wire into a format that Apache Camel
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Validates a message based on an expression
+Validates the message against a predicate expression and throws a PredicateValidationException if the validation fails
]]>
</xs:documentation>
</xs:annotation>
@@ -2376,7 +2255,7 @@ Validates a message based on an expression
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure validators.
+Container for defining data type validator definitions
]]>
</xs:documentation>
</xs:annotation>
@@ -2385,7 +2264,7 @@ To configure validators.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A single value
+Holds a single value, typically used as a child element in collection-based configurations
]]>
</xs:documentation>
</xs:annotation>
@@ -2403,7 +2282,7 @@ Gets a variable
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Call a wasm (web assembly) function.
+Call a wasm (web assembly) function
]]>
</xs:documentation>
</xs:annotation>
@@ -2412,7 +2291,7 @@ Call a wasm (web assembly) function.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Uses a weighted load distribution ratio for each server with respect to others.
+Load balancer that distributes messages across endpoints according to configured weight ratios
]]>
</xs:documentation>
</xs:annotation>
@@ -2421,7 +2300,7 @@ Uses a weighted load distribution ratio for each server with respect to others.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Triggers a route when the expression evaluates to true
+Defines a conditional branch within a Choice EIP that executes when its predicate evaluates to true
]]>
</xs:documentation>
</xs:annotation>
@@ -2430,8 +2309,8 @@ Triggers a route when the expression evaluates to true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Routes a copy of a message (or creates a new message) to a secondary destination while continue routing the original
-message.
+Sends a copy of the message to a secondary endpoint without affecting the original route flow. The tapped message is
+sent asynchronously in a separate thread
]]>
</xs:documentation>
</xs:annotation>
@@ -2440,7 +2319,7 @@ message.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Encrypt and decrypt XML payloads using Apache Santuario.
+Encrypt and decrypt XML payloads using Apache Santuario
]]>
</xs:documentation>
</xs:annotation>
@@ -2449,7 +2328,7 @@ Encrypt and decrypt XML payloads using Apache Santuario.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates an XPath expression against an XML payload.
+Evaluates an XPath expression against an XML payload
]]>
</xs:documentation>
</xs:annotation>
@@ -2458,7 +2337,7 @@ Evaluates an XPath expression against an XML payload.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Evaluates an XQuery expressions against an XML payload.
+Evaluates an XQuery expressions against an XML payload
]]>
</xs:documentation>
</xs:annotation>
@@ -2467,7 +2346,7 @@ Evaluates an XQuery expressions against an XML payload.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Tokenize XML payloads.
+Tokenize XML payloads
]]>
</xs:documentation>
</xs:annotation>
@@ -2476,7 +2355,7 @@ Tokenize XML payloads.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Marshal and unmarshal Java objects to and from YAML.
+Marshal and unmarshal Java objects to and from YAML
]]>
</xs:documentation>
</xs:annotation>
@@ -2485,7 +2364,7 @@ Marshal and unmarshal Java objects to and from YAML.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Compress and decompress streams using java.util.zip.Deflater and java.util.zip.Inflater.
+Compress and decompress streams using java.util.zip.Deflater and java.util.zip.Inflater
]]>
</xs:documentation>
</xs:annotation>
@@ -2494,16 +2373,7 @@ Compress and decompress streams using java.util.zip.Deflater and java.util.zip.I
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Compression and decompress streams using java.util.zip.ZipStream.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element name="zookeeperServiceDiscovery" type="tns:zooKeeperServiceCallServiceDiscoveryConfiguration">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Deprecated: null
+Compression and decompress streams using java.util.zip.Zip*Stream
]]>
</xs:documentation>
</xs:annotation>
@@ -2971,138 +2841,196 @@ Whether to use a scheduled thread pool. Default value: false
<xs:complexContent>
<xs:extension base="tns:identifiedType">
<xs:sequence/>
- <xs:attribute name="disabled" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Disable JMI (default false). Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="onlyRegisterProcessorWithCustomId" type="xs:string">
+ <xs:attribute name="disabled" type="xs:string"/>
+ <xs:attribute name="onlyRegisterProcessorWithCustomId" type="xs:string"/>
+ <xs:attribute name="mbeanServerDefaultDomain" type="xs:string"/>
+ <xs:attribute name="mbeanObjectDomainName" type="xs:string"/>
+ <xs:attribute name="usePlatformMBeanServer" type="xs:string"/>
+ <xs:attribute name="registerAlways" type="xs:string"/>
+ <xs:attribute name="registerNewRoutes" type="xs:string"/>
+ <xs:attribute name="statisticsLevel" type="xs:string"/>
+ <xs:attribute name="mbeansLevel" type="xs:string"/>
+ <xs:attribute name="loadStatisticsEnabled" type="xs:string"/>
+ <xs:attribute name="endpointRuntimeStatisticsEnabled" type="xs:string"/>
+ <xs:attribute name="includeHostName" type="xs:string"/>
+ <xs:attribute name="useHostIPAddress" type="xs:string"/>
+ <xs:attribute name="mask" type="xs:string"/>
+ <xs:attribute name="updateRouteEnabled" type="xs:string"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="camelPropertyPlaceholderDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:identifiedType">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" ref="tns:propertiesFunction"/>
+ <xs:element maxOccurs="unbounded" minOccurs="0" ref="tns:propertiesLocation"/>
+ </xs:sequence>
+ <xs:attribute name="location" type="xs:string"/>
+ <xs:attribute name="encoding" type="xs:string"/>
+ <xs:attribute name="ignoreMissingLocation" type="xs:boolean"/>
+ <xs:attribute name="nestedPlaceholder" type="xs:boolean"/>
+ <xs:attribute name="propertiesParserRef" type="xs:string"/>
+ <xs:attribute name="defaultFallbackEnabled" type="xs:boolean"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="camelPropertyPlaceholderFunctionDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:identifiedType">
+ <xs:sequence/>
+ <xs:attribute name="ref" type="xs:string" use="required"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="camelPropertyPlaceholderLocationDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:identifiedType">
+ <xs:sequence/>
+ <xs:attribute name="resolver" type="xs:string"/>
+ <xs:attribute name="path" type="xs:string" use="required"/>
+ <xs:attribute name="optional" type="xs:boolean"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="camelRouteControllerDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:identifiedType">
+ <xs:sequence/>
+ <xs:attribute name="supervising" type="xs:string"/>
+ <xs:attribute name="includeRoutes" type="xs:string"/>
+ <xs:attribute name="excludeRoutes" type="xs:string"/>
+ <xs:attribute name="threadPoolSize" type="xs:string"/>
+ <xs:attribute name="initialDelay" type="xs:string"/>
+ <xs:attribute name="backOffDelay" type="xs:string"/>
+ <xs:attribute name="backOffMaxDelay" type="xs:string"/>
+ <xs:attribute name="backOffMaxElapsedTime" type="xs:string"/>
+ <xs:attribute name="backOffMaxAttempts" type="xs:string"/>
+ <xs:attribute name="backOffMultiplier" type="xs:string"/>
+ <xs:attribute name="unhealthyOnExhausted" type="xs:string"/>
+ <xs:attribute name="unhealthyOnRestarting" type="xs:string"/>
+ <xs:attribute name="loggingLevel" type="xs:string"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="camelStreamCachingStrategyDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:identifiedType">
+ <xs:sequence/>
+ <xs:attribute name="enabled" type="xs:string"/>
+ <xs:attribute name="spoolEnabled" type="xs:string"/>
+ <xs:attribute name="allowClasses" type="xs:string"/>
+ <xs:attribute name="denyClasses" type="xs:string"/>
+ <xs:attribute name="spoolDirectory" type="xs:string"/>
+ <xs:attribute name="spoolCipher" type="xs:string"/>
+ <xs:attribute name="spoolThreshold" type="xs:string"/>
+ <xs:attribute name="spoolUsedHeapMemoryThreshold" type="xs:string"/>
+ <xs:attribute name="spoolUsedHeapMemoryLimit" type="xs:string"/>
+ <xs:attribute name="spoolRules" type="xs:string"/>
+ <xs:attribute name="bufferSize" type="xs:string"/>
+ <xs:attribute name="removeSpoolDirectoryWhenStopping" type="xs:string"/>
+ <xs:attribute name="statisticsEnabled" type="xs:string"/>
+ <xs:attribute name="anySpoolRules" type="xs:string"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="patternBasedPackageScanFilter">
+ <xs:sequence/>
+ </xs:complexType>
+ <xs:complexType abstract="true" name="abstractJsseUtilFactoryBean">
+ <xs:complexContent>
+ <xs:extension base="tns:abstractCamelFactoryBean">
+ <xs:sequence/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType abstract="true" name="abstractKeyManagersParametersFactoryBean">
+ <xs:complexContent>
+ <xs:extension base="tns:abstractJsseUtilFactoryBean">
+ <xs:sequence/>
+ <xs:attribute name="keyPassword" type="xs:string"/>
+ <xs:attribute name="provider" type="xs:string"/>
+ <xs:attribute name="algorithm" type="xs:string"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType abstract="true" name="abstractKeyStoreParametersFactoryBean">
+ <xs:complexContent>
+ <xs:extension base="tns:abstractJsseUtilFactoryBean">
+ <xs:sequence/>
+ <xs:attribute name="resource" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Only register processor if a custom id was defined for it. Default value: false
+The keystore to load. The keystore is by default loaded from classpath. If you must load from file system, then use
+file: as prefix. file:nameOfFile (to refer to the file system) classpath:nameOfFile (to refer to the classpath; default)
+http:uri (to load the resource using HTTP) ref:nameOfBean (to lookup an existing KeyStore instance from the registry,
+for example for testing and development).
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="mbeanServerDefaultDomain" type="xs:string">
+ <xs:attribute name="password" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-MBean server default domain name (default org.apache.camel). Default value: org.apache.camel
+The password for reading/opening/verifying the key store.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="mbeanObjectDomainName" type="xs:string">
+ <xs:attribute name="type" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-MBean object domain name (default org.apache.camel). Default value: org.apache.camel
+The type of the key store to create and load. See
+https://docs.oracle.com/en/java/javase/17/docs/specs/security/standard-names.html.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="usePlatformMBeanServer" type="xs:string">
+ <xs:attribute name="provider" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A flag that indicates whether the platform mbean server should be used. Default value: true
+The provider identifier for instantiating the key store.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="registerAlways" type="xs:string">
+ <xs:attribute name="keyStore" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A flag that indicates whether to register mbeans always. Default value: false
+To lookup an existing KeyStore instance from the registry, for example for testing and development.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="registerNewRoutes" type="xs:string">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType abstract="true" name="abstractSecureRandomParametersFactoryBean">
+ <xs:complexContent>
+ <xs:extension base="tns:abstractJsseUtilFactoryBean">
+ <xs:sequence/>
+ <xs:attribute name="algorithm" type="xs:string" use="required">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A flag that indicates whether to register mbeans when starting new routes. Default value: true
+The Random Number Generator algorithm identifier for the SecureRandom factory method used to create the SecureRandom
+represented by this object's configuration. See
+https://docs.oracle.com/en/java/javase/17/docs/specs/security/standard-names.html.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="statisticsLevel" type="xs:string">
+ <xs:attribute name="provider" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Level of granularity for performance statistics enabled. Default value: Default
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="mbeansLevel" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Sets the mbeans registration level. The default value is Default. Default value: Default
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="loadStatisticsEnabled" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A flag that indicates whether Load statistics is enabled. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="endpointRuntimeStatisticsEnabled" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A flag that indicates whether endpoint runtime statistics is enabled. Default value: true
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="includeHostName" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A flag that indicates whether to include hostname in JMX MBean names. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="useHostIPAddress" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A flag that indicates whether to use hostname or IP Address in the service url. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="mask" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A flag that indicates whether to remove detected sensitive information (such as passwords) from MBean names and
-attributes. Default value: true
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="updateRouteEnabled" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Sets whether updating routes via JMX is allowed (is default disabled). Default value: false
+The provider identifier for the SecureRandom factory method used to create the SecureRandom represented by this object's
+configuration.
]]>
</xs:documentation>
</xs:annotation>
@@ -3110,68 +3038,157 @@ Sets whether updating routes via JMX is allowed (is default disabled). Default v
</xs:extension>
</xs:complexContent>
</xs:complexType>
- <xs:complexType name="camelPropertyPlaceholderDefinition">
+ <xs:complexType abstract="true" name="abstractTrustManagersParametersFactoryBean">
<xs:complexContent>
- <xs:extension base="tns:identifiedType">
+ <xs:extension base="tns:abstractJsseUtilFactoryBean">
+ <xs:sequence/>
+ <xs:attribute name="provider" type="xs:string"/>
+ <xs:attribute name="algorithm" type="xs:string"/>
+ <xs:attribute name="trustManager" type="xs:string"/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="cipherSuitesParameters">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="cipherSuite" nillable="true" type="xs:string"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="filterParameters">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="include" nillable="true" type="xs:string"/>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="exclude" nillable="true" type="xs:string"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="namedGroupsParameters">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="namedGroup" nillable="true" type="xs:string"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="sniHostNames">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="sniHostName" type="xs:string"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="secureSocketProtocolsParameters">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="secureSocketProtocol" nillable="true" type="xs:string"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="signatureSchemesParameters">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="signatureScheme" nillable="true" type="xs:string"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="a2ASubTaskDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:output">
<xs:sequence>
- <xs:element maxOccurs="unbounded" minOccurs="0" ref="tns:propertiesFunction"/>
- <xs:element maxOccurs="unbounded" minOccurs="0" ref="tns:propertiesLocation"/>
+ <xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
+ <xs:element ref="tns:aggregate"/>
+ <xs:element ref="tns:bean"/>
+ <xs:element ref="tns:doCatch"/>
+ <xs:element ref="tns:choice"/>
+ <xs:element ref="tns:circuitBreaker"/>
+ <xs:element ref="tns:claimCheck"/>
+ <xs:element ref="tns:convertBodyTo"/>
+ <xs:element ref="tns:convertHeaderTo"/>
+ <xs:element ref="tns:convertVariableTo"/>
+ <xs:element ref="tns:delay"/>
+ <xs:element ref="tns:dynamicRouter"/>
+ <xs:element ref="tns:enrich"/>
+ <xs:element ref="tns:filter"/>
+ <xs:element ref="tns:doFinally"/>
+ <xs:element ref="tns:idempotentConsumer"/>
+ <xs:element ref="tns:intercept"/>
+ <xs:element ref="tns:interceptFrom"/>
+ <xs:element ref="tns:interceptSendToEndpoint"/>
+ <xs:element ref="tns:kamelet"/>
+ <xs:element ref="tns:loadBalance"/>
+ <xs:element ref="tns:log"/>
+ <xs:element ref="tns:loop"/>
+ <xs:element ref="tns:marshal"/>
+ <xs:element ref="tns:multicast"/>
+ <xs:element ref="tns:onCompletion"/>
+ <xs:element ref="tns:onException"/>
+ <xs:element ref="tns:pausable"/>
+ <xs:element ref="tns:pipeline"/>
+ <xs:element ref="tns:policy"/>
+ <xs:element ref="tns:poll"/>
+ <xs:element ref="tns:pollEnrich"/>
+ <xs:element ref="tns:process"/>
+ <xs:element ref="tns:recipientList"/>
+ <xs:element ref="tns:removeHeader"/>
+ <xs:element ref="tns:removeHeaders"/>
+ <xs:element ref="tns:removeProperties"/>
+ <xs:element ref="tns:removeProperty"/>
+ <xs:element ref="tns:removeVariable"/>
+ <xs:element ref="tns:resequence"/>
+ <xs:element ref="tns:resumable"/>
+ <xs:element ref="tns:rollback"/>
+ <xs:element ref="tns:route"/>
+ <xs:element ref="tns:routingSlip"/>
+ <xs:element ref="tns:saga"/>
+ <xs:element ref="tns:sample"/>
+ <xs:element ref="tns:script"/>
+ <xs:element ref="tns:setBody"/>
+ <xs:element ref="tns:setExchangePattern"/>
+ <xs:element ref="tns:setHeader"/>
+ <xs:element ref="tns:setHeaders"/>
+ <xs:element ref="tns:setProperty"/>
+ <xs:element ref="tns:setVariable"/>
+ <xs:element ref="tns:setVariables"/>
+ <xs:element ref="tns:sort"/>
+ <xs:element ref="tns:split"/>
+ <xs:element ref="tns:step"/>
+ <xs:element ref="tns:stop"/>
+ <xs:element ref="tns:threads"/>
+ <xs:element ref="tns:throttle"/>
+ <xs:element ref="tns:throwException"/>
+ <xs:element ref="tns:to"/>
+ <xs:element ref="tns:toD"/>
+ <xs:element ref="tns:tokenizer"/>
+ <xs:element ref="tns:transacted"/>
+ <xs:element ref="tns:transformDataType"/>
+ <xs:element ref="tns:transform"/>
+ <xs:element ref="tns:doTry"/>
+ <xs:element ref="tns:unmarshal"/>
+ <xs:element ref="tns:validate"/>
+ <xs:element ref="tns:wireTap"/>
+ </xs:choice>
</xs:sequence>
- <xs:attribute name="location" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A list of locations to load properties. You can use comma to separate multiple locations. This option will override any
-default locations and only use the locations from this option.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="encoding" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Encoding to use when loading properties file from the file system or classpath. If no encoding has been set, then the
-properties files is loaded using ISO-8859-1 encoding (latin-1) as documented by
-java.util.Properties#load(java.io.InputStream).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="ignoreMissingLocation" type="xs:boolean">
+ <xs:attribute name="emitBefore" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to silently ignore if a location cannot be located, such as a properties file not found. Default value: false
+Simple expression template to emit before the nested steps run.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="nestedPlaceholder" type="xs:boolean">
+ <xs:attribute name="emitAfter" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to support nested property placeholders. A nested placeholder, means that a placeholder, has also a placeholder,
-that should be resolved (recursively). Default value: true
+Simple expression template to emit after the nested steps complete successfully.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="propertiesParserRef" type="xs:string">
+ <xs:attribute name="emitOnError" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to a custom PropertiesParser to be used.
+Simple expression template to emit when the nested steps fail.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="defaultFallbackEnabled" type="xs:boolean">
+ <xs:attribute name="failIfNoTaskContext" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If false, the component does not attempt to find a default for the key by looking after the colon separator. Default
-value: true
+Whether to fail if the current Exchange does not have an active A2A task context. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -3179,49 +3196,23 @@ value: true
</xs:extension>
</xs:complexContent>
</xs:complexType>
- <xs:complexType name="camelPropertyPlaceholderFunctionDefinition">
+ <xs:complexType name="output">
<xs:complexContent>
- <xs:extension base="tns:identifiedType">
+ <xs:extension base="tns:processorDefinition">
<xs:sequence/>
- <xs:attribute name="ref" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Reference to the custom properties function to lookup in the registry.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
- <xs:complexType name="camelPropertyPlaceholderLocationDefinition">
+ <xs:complexType abstract="true" name="processorDefinition">
<xs:complexContent>
- <xs:extension base="tns:identifiedType">
+ <xs:extension base="tns:optionalIdentifiedDefinition">
<xs:sequence/>
- <xs:attribute name="resolver" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The resolver to use to locate the location. Default value: classpath
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="path" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Property locations to use.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="optional" type="xs:boolean">
+ <xs:attribute name="disabled" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If the location is optional. Default value: false
+Whether to disable this EIP from the route during build time. Once an EIP has been disabled then it cannot be enabled
+later at runtime. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -3229,1173 +3220,691 @@ If the location is optional. Default value: false
</xs:extension>
</xs:complexContent>
</xs:complexType>
- <xs:complexType name="camelRouteControllerDefinition">
- <xs:complexContent>
- <xs:extension base="tns:identifiedType">
- <xs:sequence/>
- <xs:attribute name="supervising" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-To enable using supervising route controller which allows Camel to start up and then, the controller takes care of
-starting the routes in a safe manner. This can be used when you want to start up Camel despite a route may otherwise
-fail fast during startup and cause Camel to fail to start up as well. By delegating the route startup to the supervising
-route controller then its manages the startup using a background thread. The controller allows to be configured with
-various settings to attempt to restart failing routes. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="includeRoutes" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ <xs:complexType abstract="true" name="optionalIdentifiedDefinition">
+ <xs:sequence/>
+ <xs:attribute name="customId" type="xs:boolean"/>
+ <xs:attribute name="description" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Pattern for filtering routes to be included as supervised. The pattern is matching on route id, and endpoint uri for the
-route. Multiple patterns can be separated by comma. For example to include all kafka routes, you can say kafka:. And to
-include routes with specific route ids myRoute,myOtherRoute. The pattern supports wildcards and uses the matcher from
-org.apache.camel.support.PatternHelper#matchPattern.
+The description for this node.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="excludeRoutes" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="id" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Pattern for filtering routes to be excluded as supervised. The pattern is matching on route id, and endpoint uri for the
-route. Multiple patterns can be separated by comma. For example to exclude all JMS routes, you can say jms:. And to
-exclude routes with specific route ids mySpecialRoute,myOtherSpecialRoute. The pattern supports wildcards and uses the
-matcher from org.apache.camel.support.PatternHelper#matchPattern.
+The id of this node.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="threadPoolSize" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="note" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-The number of threads used by the scheduled thread pool that are used for restarting routes. The pool uses 1 thread by
-default, but you can increase this to allow the controller to concurrently attempt to restart multiple routes in case
-more than one route has problems starting. Default value: 1
+The note for this node.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="initialDelay" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:complexType>
+ <xs:complexType name="aggregateDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:output">
+ <xs:sequence>
+ <xs:element name="correlationExpression" type="tns:expressionSubElementDefinition">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Initial delay in milli seconds before the route controller starts, after CamelContext has been started.
+The expression used to calculate the correlation key to use for aggregation. Exchanges with the same correlation key are
+aggregated together. If the correlation key cannot be evaluated an Exception is thrown.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="backOffDelay" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element minOccurs="0" name="completionPredicate" type="tns:expressionSubElementDefinition">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Backoff delay in millis when restarting a route that failed to startup. Default value: 2000
+A predicate to indicate when an aggregated exchange is complete. If not specified and the AggregationStrategy implements
+Predicate, it will be used as the completionPredicate.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="backOffMaxDelay" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element minOccurs="0" name="completionTimeoutExpression" type="tns:expressionSubElementDefinition">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Backoff maximum delay in millis when restarting a route that failed to startup.
+Time in millis that an aggregated exchange should be inactive before its complete (timeout), evaluated as an expression
+allowing dynamic timeout values.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="backOffMaxElapsedTime" type="xs:string">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element minOccurs="0" name="completionSizeExpression" type="tns:expressionSubElementDefinition">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Number of messages aggregated before the aggregation is complete, evaluated as an expression allowing dynamic size
+values.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element minOccurs="0" ref="tns:optimisticLockRetryPolicy"/>
+ <xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
+ <xs:element ref="tns:aggregate"/>
+ <xs:element ref="tns:bean"/>
+ <xs:element ref="tns:doCatch"/>
+ <xs:element ref="tns:choice"/>
+ <xs:element ref="tns:circuitBreaker"/>
+ <xs:element ref="tns:claimCheck"/>
+ <xs:element ref="tns:convertBodyTo"/>
+ <xs:element ref="tns:convertHeaderTo"/>
+ <xs:element ref="tns:convertVariableTo"/>
+ <xs:element ref="tns:delay"/>
+ <xs:element ref="tns:dynamicRouter"/>
+ <xs:element ref="tns:enrich"/>
+ <xs:element ref="tns:filter"/>
+ <xs:element ref="tns:doFinally"/>
+ <xs:element ref="tns:idempotentConsumer"/>
+ <xs:element ref="tns:intercept"/>
+ <xs:element ref="tns:interceptFrom"/>
+ <xs:element ref="tns:interceptSendToEndpoint"/>
+ <xs:element ref="tns:kamelet"/>
+ <xs:element ref="tns:loadBalance"/>
+ <xs:element ref="tns:log"/>
+ <xs:element ref="tns:loop"/>
+ <xs:element ref="tns:marshal"/>
+ <xs:element ref="tns:multicast"/>
+ <xs:element ref="tns:onCompletion"/>
+ <xs:element ref="tns:onException"/>
+ <xs:element ref="tns:pausable"/>
+ <xs:element ref="tns:pipeline"/>
+ <xs:element ref="tns:policy"/>
+ <xs:element ref="tns:poll"/>
+ <xs:element ref="tns:pollEnrich"/>
+ <xs:element ref="tns:process"/>
+ <xs:element ref="tns:recipientList"/>
+ <xs:element ref="tns:removeHeader"/>
+ <xs:element ref="tns:removeHeaders"/>
+ <xs:element ref="tns:removeProperties"/>
+ <xs:element ref="tns:removeProperty"/>
+ <xs:element ref="tns:removeVariable"/>
+ <xs:element ref="tns:resequence"/>
+ <xs:element ref="tns:resumable"/>
+ <xs:element ref="tns:rollback"/>
+ <xs:element ref="tns:route"/>
+ <xs:element ref="tns:routingSlip"/>
+ <xs:element ref="tns:saga"/>
+ <xs:element ref="tns:sample"/>
+ <xs:element ref="tns:script"/>
+ <xs:element ref="tns:setBody"/>
+ <xs:element ref="tns:setExchangePattern"/>
+ <xs:element ref="tns:setHeader"/>
+ <xs:element ref="tns:setHeaders"/>
+ <xs:element ref="tns:setProperty"/>
+ <xs:element ref="tns:setVariable"/>
+ <xs:element ref="tns:setVariables"/>
+ <xs:element ref="tns:sort"/>
+ <xs:element ref="tns:split"/>
+ <xs:element ref="tns:step"/>
+ <xs:element ref="tns:stop"/>
+ <xs:element ref="tns:threads"/>
+ <xs:element ref="tns:throttle"/>
+ <xs:element ref="tns:throwException"/>
+ <xs:element ref="tns:to"/>
+ <xs:element ref="tns:toD"/>
+ <xs:element ref="tns:tokenizer"/>
+ <xs:element ref="tns:transacted"/>
+ <xs:element ref="tns:transformDataType"/>
+ <xs:element ref="tns:transform"/>
+ <xs:element ref="tns:doTry"/>
+ <xs:element ref="tns:unmarshal"/>
+ <xs:element ref="tns:validate"/>
+ <xs:element ref="tns:wireTap"/>
+ </xs:choice>
+ </xs:sequence>
+ <xs:attribute name="parallelProcessing" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Backoff maximum elapsed time in millis, after which the backoff should be considered exhausted and no more attempts
-should be made.
+When completed exchanges are sent out of the aggregator, this option indicates whether Camel should use a thread pool
+with multiple threads for concurrency. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="backOffMaxAttempts" type="xs:string">
+ <xs:attribute name="optimisticLocking" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Backoff maximum number of attempts to restart a route that failed to startup. When this threshold has been exceeded then
-the controller will give up attempting to restart the route, and the route will remain as stopped.
+Turns on optimistic locking, which requires the aggregation repository to implement
+OptimisticLockingAggregationRepository. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="backOffMultiplier" type="xs:string">
+ <xs:attribute name="optimisticLockingSyncRetry" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Backoff multiplier to use for exponential backoff. This is used to extend the delay between restart attempts. Default
-value: 1.0
+When optimistic locking is enabled, retries happen synchronously in the same thread instead of being scheduled on a
+background thread. This preserves transaction context for repositories that require single-thread transactional
+guarantees. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="unhealthyOnExhausted" type="xs:string">
+ <xs:attribute name="executorService" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to mark the route as unhealthy (down) when all restarting attempts (backoff) have failed and the route is not
-successfully started and the route manager is giving up. Setting this to true allows health checks to know about this
-and can report the Camel application as DOWN. Default value: false
+Reference to a custom thread pool to use for parallel processing and sending out aggregated exchanges.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="unhealthyOnRestarting" type="xs:string">
+ <xs:attribute name="timeoutCheckerExecutorService" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to mark the route as unhealthy (down) when the route failed to initially start, and is being controlled for
-restarting (backoff). Setting this to true allows health checks to know about this and can report the Camel application
-as DOWN. Default value: false
+Reference to a custom thread pool for the background completion timeout checker.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="loggingLevel" type="xs:string">
+ <xs:attribute name="aggregateController" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the logging level used for logging route activity (such as starting and stopping routes). The default logging level
-is DEBUG. Default value: DEBUG
+Reference to an AggregateController to allow external sources to control this aggregator.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="camelStreamCachingStrategyDefinition">
- <xs:complexContent>
- <xs:extension base="tns:identifiedType">
- <xs:sequence/>
- <xs:attribute name="enabled" type="xs:string">
+ <xs:attribute name="aggregationRepository" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether stream caching is enabled or not. While stream types (like StreamSource, InputStream and Reader) are
-commonly used in messaging for performance reasons, they also have an important drawback: they can only be read once. In
-order to be able to work with message content multiple times, the stream needs to be cached. Streams are cached in
-memory only (by default). If streamCachingSpoolEnabled=true, then, for large stream messages (over 128 KB by default)
-will be cached in a temporary file instead, and Camel will handle deleting the temporary file once the cached stream is
-no longer necessary. Default is true. Default value: true
+Reference to the AggregationRepository to use. By default uses MemoryAggregationRepository.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="spoolEnabled" type="xs:string">
+ <xs:attribute name="aggregationStrategy" type="xs:string" use="required">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To enable stream caching spooling to disk. This means, for large stream messages (over 128 KB by default) will be cached
-in a temporary file instead, and Camel will handle deleting the temporary file once the cached stream is no longer
-necessary. Default is false. Default value: false
+The AggregationStrategy to use. Required. Merges each incoming exchange with the existing already merged exchanges. At
+first call the oldExchange parameter is null.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="allowClasses" type="xs:string">
+ <xs:attribute name="aggregationStrategyMethodName" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To filter stream caching of a given set of allowed/denied classes. By default, all classes that are java.io.InputStream
-is allowed. Multiple class names can be separated by comma.
+The method name to use when using a POJO as the AggregationStrategy.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="denyClasses" type="xs:string">
+ <xs:attribute name="aggregationStrategyMethodAllowNull" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To filter stream caching of a given set of allowed/denied classes. By default, all classes that are java.io.InputStream
-is allowed. Multiple class names can be separated by comma.
+If true then null is used as the oldExchange at the very first aggregation, when using POJOs as the AggregationStrategy.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="spoolDirectory" type="xs:string">
+ <xs:attribute name="completionSize" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the spool (temporary) directory to use for overflow and spooling to disk. If no spool directory has been explicit
-configured, then a temporary directory is created in the java.io.tmpdir directory.
+Number of messages aggregated before the aggregation is complete. Can also be set as an expression via
+completionSizeExpression.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="spoolCipher" type="xs:string">
+ <xs:attribute name="completionInterval" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a cipher name to use when spooling to disk to write with encryption. By default the data is not encrypted.
+A repeating period by which the aggregator will complete all current aggregated exchanges. Cannot be used together with
+completionTimeout.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="spoolThreshold" type="xs:string">
+ <xs:attribute name="completionTimeout" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Threshold in bytes when overflow to disk is activated. The default threshold is
-org.apache.camel.StreamCache#DEFAULT_SPOOL_THRESHOLD bytes (eg 128kb). Use -1 to disable overflow to disk. Default
-value: 131072
+Time that an aggregated exchange should be inactive before its complete (timeout). Cannot be used together with
+completionInterval.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="spoolUsedHeapMemoryThreshold" type="xs:string">
+ <xs:attribute name="completionTimeoutCheckerInterval" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a percentage (1-99) of used heap memory threshold to activate spooling to disk.
+Interval in millis for the background task that checks for completion timeouts. Default is 1000 (1 second). Default
+value: 1000
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="spoolUsedHeapMemoryLimit" type="xs:string">
+ <xs:attribute name="completionFromBatchConsumer" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets what the upper bounds should be when spoolUsedHeapMemoryThreshold is in use.
+Enables batch completion mode where aggregation completes based on the total number of exchanges reported by a batch
+consumer. Cannot be used together with discardOnAggregationFailure. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="spoolRules" type="xs:string">
+ <xs:attribute name="completionOnNewCorrelationGroup" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to one or more custom org.apache.camel.spi.StreamCachingStrategy.SpoolRule to use. Multiple rules can be
-separated by comma.
+Enables completion on all previous groups when a new incoming correlation group starts. Only one correlation group can
+be in progress at a time. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="bufferSize" type="xs:string">
+ <xs:attribute name="eagerCheckCompletion" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the buffer size to use when allocating in-memory buffers used for in-memory stream caches. The default size is
-org.apache.camel.util.IOHelper#DEFAULT_BUFFER_SIZE. Default value: 16384
+If enabled then the completion predicate evaluates against the incoming exchange. Otherwise it evaluates against the
+aggregated exchange. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="removeSpoolDirectoryWhenStopping" type="xs:string">
+ <xs:attribute name="ignoreInvalidCorrelationKeys" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to remove the temporary directory when stopping. This option is default true. Default value: true
+If enabled then a correlation key that cannot be evaluated is logged and ignored, instead of throwing an exception.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="statisticsEnabled" type="xs:string">
+ <xs:attribute name="closeCorrelationKeyOnCompletion" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether statistics is enabled. Default value: false
+Closes a correlation key when its complete. Late arriving exchanges with a closed correlation key will throw a
+ClosedCorrelationKeyException. The value is the maximum cache size of closed keys. Use 0 for unbounded.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="anySpoolRules" type="xs:string">
+ <xs:attribute name="discardOnCompletionTimeout" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether if just any of the org.apache.camel.spi.StreamCachingStrategy.SpoolRule rules returns true then
-shouldSpoolCache(long) returns true. If this option is false, then all the
-org.apache.camel.spi.StreamCachingStrategy.SpoolRule must return true. The default value is false which means that all
-the rules must return true. Default value: false
+If enabled then the aggregated message is discarded (dropped) on completion timeout instead of being sent out of the
+aggregator. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="patternBasedPackageScanFilter">
- <xs:sequence/>
- </xs:complexType>
- <xs:complexType abstract="true" name="abstractJsseUtilFactoryBean">
- <xs:complexContent>
- <xs:extension base="tns:abstractCamelFactoryBean">
- <xs:sequence/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType abstract="true" name="abstractKeyManagersParametersFactoryBean">
- <xs:complexContent>
- <xs:extension base="tns:abstractJsseUtilFactoryBean">
- <xs:sequence/>
- <xs:attribute name="keyPassword" type="xs:string"/>
- <xs:attribute name="provider" type="xs:string"/>
- <xs:attribute name="algorithm" type="xs:string"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType abstract="true" name="abstractKeyStoreParametersFactoryBean">
- <xs:complexContent>
- <xs:extension base="tns:abstractJsseUtilFactoryBean">
- <xs:sequence/>
- <xs:attribute name="resource" type="xs:string">
+ <xs:attribute name="discardOnAggregationFailure" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The keystore to load. The keystore is by default loaded from classpath. If you must load from file system, then use
-file: as prefix. file:nameOfFile (to refer to the file system) classpath:nameOfFile (to refer to the classpath; default)
-http:uri (to load the resource using HTTP) ref:nameOfBean (to lookup an existing KeyStore instance from the registry,
-for example for testing and development).
+If enabled then the partly aggregated message is discarded when aggregation failed (an exception was thrown from
+AggregationStrategy). Cannot be used together with completionFromBatchConsumer. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="password" type="xs:string">
+ <xs:attribute name="forceCompletionOnStop" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The password for reading/opening/verifying the key store.
+If enabled then all current aggregated exchanges are completed when the context is stopped. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="type" type="xs:string">
+ <xs:attribute name="completeAllOnStop" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The type of the key store to create and load. See
-https://docs.oracle.com/en/java/javase/17/docs/specs/security/standard-names.html.
+If enabled then waits to complete all current and partial (pending) aggregated exchanges when the context is stopped,
+ensuring the aggregation repository is empty before shutdown. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="provider" type="xs:string">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="expressionSubElementDefinition">
+ <xs:choice>
+ <xs:element ref="tns:expressionDefinition"/>
+ <xs:element ref="tns:csimple"/>
+ <xs:element ref="tns:constant"/>
+ <xs:element ref="tns:datasonnet"/>
+ <xs:element ref="tns:exchangeProperty"/>
+ <xs:element ref="tns:groovy"/>
+ <xs:element ref="tns:header"/>
+ <xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
+ <xs:element ref="tns:java"/>
+ <xs:element ref="tns:js"/>
+ <xs:element ref="tns:joor"/>
+ <xs:element ref="tns:jq"/>
+ <xs:element ref="tns:jsonpath"/>
+ <xs:element ref="tns:language"/>
+ <xs:element ref="tns:method"/>
+ <xs:element ref="tns:mvel"/>
+ <xs:element ref="tns:ognl"/>
+ <xs:element ref="tns:python"/>
+ <xs:element ref="tns:ref"/>
+ <xs:element ref="tns:simple"/>
+ <xs:element ref="tns:spel"/>
+ <xs:element ref="tns:tokenize"/>
+ <xs:element ref="tns:variable"/>
+ <xs:element ref="tns:wasm"/>
+ <xs:element ref="tns:xtokenize"/>
+ <xs:element ref="tns:xpath"/>
+ <xs:element ref="tns:xquery"/>
+ </xs:choice>
+ </xs:complexType>
+ <xs:complexType name="expression">
+ <xs:simpleContent>
+ <xs:extension base="xs:string">
+ <xs:attribute name="id" type="xs:ID">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The provider identifier for instantiating the key store.
+The id of this node.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="keyStore" type="xs:string">
+ <xs:attribute name="trim" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To lookup an existing KeyStore instance from the registry, for example for testing and development.
+Whether to trim the source code to remove leading and trailing whitespaces and line breaks. Default value: true
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
- </xs:complexContent>
+ </xs:simpleContent>
</xs:complexType>
- <xs:complexType abstract="true" name="abstractSecureRandomParametersFactoryBean">
- <xs:complexContent>
- <xs:extension base="tns:abstractJsseUtilFactoryBean">
- <xs:sequence/>
- <xs:attribute name="algorithm" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ <xs:complexType name="optimisticLockRetryPolicyDefinition">
+ <xs:sequence/>
+ <xs:attribute name="maximumRetries" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-The Random Number Generator algorithm identifier for the SecureRandom factory method used to create the SecureRandom
-represented by this object's configuration. See
-https://docs.oracle.com/en/java/javase/17/docs/specs/security/standard-names.html.
+Sets the maximum number of retries before giving up on acquiring the optimistic lock.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="provider" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The provider identifier for the SecureRandom factory method used to create the SecureRandom represented by this object's
-configuration.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType abstract="true" name="abstractTrustManagersParametersFactoryBean">
- <xs:complexContent>
- <xs:extension base="tns:abstractJsseUtilFactoryBean">
- <xs:sequence/>
- <xs:attribute name="provider" type="xs:string"/>
- <xs:attribute name="algorithm" type="xs:string"/>
- <xs:attribute name="trustManager" type="xs:string"/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="cipherSuitesParameters">
- <xs:sequence>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="cipherSuite" nillable="true" type="xs:string"/>
- </xs:sequence>
- </xs:complexType>
- <xs:complexType name="filterParameters">
- <xs:sequence>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="include" nillable="true" type="xs:string"/>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="exclude" nillable="true" type="xs:string"/>
- </xs:sequence>
- </xs:complexType>
- <xs:complexType name="sniHostNames">
- <xs:sequence>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="sniHostName" type="xs:string"/>
- </xs:sequence>
- </xs:complexType>
- <xs:complexType name="secureSocketProtocolsParameters">
- <xs:sequence>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="secureSocketProtocol" nillable="true" type="xs:string"/>
- </xs:sequence>
- </xs:complexType>
- <xs:complexType name="output">
- <xs:complexContent>
- <xs:extension base="tns:processorDefinition">
- <xs:sequence/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType abstract="true" name="processorDefinition">
- <xs:complexContent>
- <xs:extension base="tns:optionalIdentifiedDefinition">
- <xs:sequence/>
- <xs:attribute name="disabled" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="retryDelay" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Disables this EIP from the route. Default value: false
+Sets the delay in milliseconds between retry attempts when the optimistic lock fails. Default value: 50
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType abstract="true" name="optionalIdentifiedDefinition">
- <xs:sequence/>
- <xs:attribute name="customId" type="xs:boolean"/>
- <xs:attribute name="description" type="xs:string">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="maximumRetryDelay" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the description of this node.
+Sets the upper bound on retry delay in milliseconds to prevent delays from growing unbounded when using exponential or
+random backoff. Default value: 1000
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="id" type="xs:string">
+ <xs:attribute name="exponentialBackOff" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the id of this node.
+Whether to enable exponential backoff, so each subsequent retry delay is doubled until the maximum retry delay is
+reached. Default value: true
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="note" type="xs:string">
+ <xs:attribute name="randomBackOff" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the note of this node.
+Whether to enable random backoff, which uses a random delay between 0 and the computed retry delay to avoid thundering
+herd problems. Default value: false
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
- <xs:complexType name="aggregateDefinition">
+ <xs:complexType name="beanDefinition">
<xs:complexContent>
- <xs:extension base="tns:output">
- <xs:sequence>
- <xs:element name="correlationExpression" type="tns:expressionSubElementDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The expression used to calculate the correlation key to use for aggregation. The Exchange which has the same correlation
-key is aggregated together. If the correlation key could not be evaluated an Exception is thrown. You can disable this
-by using the ignoreBadCorrelationKeys option.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element minOccurs="0" name="completionPredicate" type="tns:expressionSubElementDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A Predicate to indicate when an aggregated exchange is complete. If this is not specified and the AggregationStrategy
-object implements Predicate, the aggregationStrategy object will be used as the completionPredicate.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element minOccurs="0" name="completionTimeoutExpression" type="tns:expressionSubElementDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Time in millis that an aggregated exchange should be inactive before its complete (timeout). This option can be set as
-either a fixed value or using an Expression which allows you to evaluate a timeout dynamically - will use Long as
-result. If both are set Camel will fallback to use the fixed value if the Expression result was null or 0. You cannot
-use this option together with completionInterval, only one of the two can be used. By default the timeout checker runs
-every second, you can use the completionTimeoutCheckerInterval option to configure how frequently to run the checker.
-The timeout is an approximation and there is no guarantee that the a timeout is triggered exactly after the timeout
-value. It is not recommended to use very low timeout values or checker intervals.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element minOccurs="0" name="completionSizeExpression" type="tns:expressionSubElementDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Number of messages aggregated before the aggregation is complete. This option can be set as either a fixed value or
-using an Expression which allows you to evaluate a size dynamically - will use Integer as result. If both are set Camel
-will fallback to use the fixed value if the Expression result was null or 0.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element minOccurs="0" ref="tns:optimisticLockRetryPolicy"/>
- <xs:choice maxOccurs="unbounded" minOccurs="0">
- <xs:element ref="tns:aggregate"/>
- <xs:element ref="tns:bean"/>
- <xs:element ref="tns:doCatch"/>
- <xs:element ref="tns:choice"/>
- <xs:element ref="tns:circuitBreaker"/>
- <xs:element ref="tns:claimCheck"/>
- <xs:element ref="tns:convertBodyTo"/>
- <xs:element ref="tns:convertHeaderTo"/>
- <xs:element ref="tns:convertVariableTo"/>
- <xs:element ref="tns:delay"/>
- <xs:element ref="tns:dynamicRouter"/>
- <xs:element ref="tns:enrich"/>
- <xs:element ref="tns:filter"/>
- <xs:element ref="tns:doFinally"/>
- <xs:element ref="tns:idempotentConsumer"/>
- <xs:element ref="tns:intercept"/>
- <xs:element ref="tns:interceptFrom"/>
- <xs:element ref="tns:interceptSendToEndpoint"/>
- <xs:element ref="tns:kamelet"/>
- <xs:element ref="tns:loadBalance"/>
- <xs:element ref="tns:log"/>
- <xs:element ref="tns:loop"/>
- <xs:element ref="tns:marshal"/>
- <xs:element ref="tns:multicast"/>
- <xs:element ref="tns:onCompletion"/>
- <xs:element ref="tns:onException"/>
- <xs:element ref="tns:pausable"/>
- <xs:element ref="tns:pipeline"/>
- <xs:element ref="tns:policy"/>
- <xs:element ref="tns:poll"/>
- <xs:element ref="tns:pollEnrich"/>
- <xs:element ref="tns:process"/>
- <xs:element ref="tns:recipientList"/>
- <xs:element ref="tns:removeHeader"/>
- <xs:element ref="tns:removeHeaders"/>
- <xs:element ref="tns:removeProperties"/>
- <xs:element ref="tns:removeProperty"/>
- <xs:element ref="tns:removeVariable"/>
- <xs:element ref="tns:resequence"/>
- <xs:element ref="tns:resumable"/>
- <xs:element ref="tns:rollback"/>
- <xs:element ref="tns:route"/>
- <xs:element ref="tns:routingSlip"/>
- <xs:element ref="tns:saga"/>
- <xs:element ref="tns:sample"/>
- <xs:element ref="tns:script"/>
- <xs:element ref="tns:setBody"/>
- <xs:element ref="tns:setExchangePattern"/>
- <xs:element ref="tns:setHeader"/>
- <xs:element ref="tns:setHeaders"/>
- <xs:element ref="tns:setProperty"/>
- <xs:element ref="tns:setVariable"/>
- <xs:element ref="tns:setVariables"/>
- <xs:element ref="tns:sort"/>
- <xs:element ref="tns:split"/>
- <xs:element ref="tns:step"/>
- <xs:element ref="tns:stop"/>
- <xs:element ref="tns:threads"/>
- <xs:element ref="tns:throttle"/>
- <xs:element ref="tns:throwException"/>
- <xs:element ref="tns:to"/>
- <xs:element ref="tns:toD"/>
- <xs:element ref="tns:tokenizer"/>
- <xs:element ref="tns:transacted"/>
- <xs:element ref="tns:transformDataType"/>
- <xs:element ref="tns:transform"/>
- <xs:element ref="tns:doTry"/>
- <xs:element ref="tns:unmarshal"/>
- <xs:element ref="tns:validate"/>
- <xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
- </xs:choice>
- </xs:sequence>
- <xs:attribute name="parallelProcessing" type="xs:string">
+ <xs:extension base="tns:noOutputDefinition">
+ <xs:sequence/>
+ <xs:attribute name="ref" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-When aggregated are completed they are being send out of the aggregator. This option indicates whether or not Camel
-should use a thread pool with multiple threads for concurrency. If no custom thread pool has been specified then Camel
-creates a default pool with 10 concurrent threads. Default value: false
+A reference to an existing bean to use, which is looked up from the registry.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="optimisticLocking" type="xs:string">
+ <xs:attribute name="method" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Turns on using optimistic locking, which requires the aggregationRepository being used, is supporting this by
-implementing org.apache.camel.spi.OptimisticLockingAggregationRepository . Default value: false
+The method name on the bean to invoke.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="executorService" type="xs:string">
+ <xs:attribute name="beanType" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If using parallelProcessing you can specify a custom thread pool to be used. In fact also if you are not using
-parallelProcessing this custom thread pool is used to send out aggregated exchanges as well.
+The class name (fully qualified) of the bean to use.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="timeoutCheckerExecutorService" type="xs:string">
+ <xs:attribute name="scope" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If using either of the completionTimeout, completionTimeoutExpression, or completionInterval options a background thread
-is created to check for the completion for every aggregator. Set this option to provide a custom thread pool to be used
-rather than creating a new thread for every aggregator.
+Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the
+lifetime of the endpoint. Default value: Singleton
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="aggregateController" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType abstract="true" name="noOutputDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:processorDefinition">
+ <xs:sequence/>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="beanFactoryDefinition">
+ <xs:sequence>
+ <xs:element minOccurs="0" name="constructors" type="tns:beanConstructorsDefinition">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-To use a org.apache.camel.processor.aggregate.AggregateController to allow external sources to control this aggregator.
+Optional constructor arguments for creating the bean. Arguments correspond to specific index of the constructor argument
+list, starting from zero.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="aggregationRepository" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element minOccurs="0" name="properties" type="tns:beanPropertiesDefinition">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-The AggregationRepository to use. Sets the custom aggregate repository to use. Will by default use
-org.apache.camel.processor.aggregate.MemoryAggregationRepository.
+Optional properties to set on the created bean.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="aggregationStrategy" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ <xs:element minOccurs="0" name="script" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-The AggregationStrategy to use. For example to lookup a bean with the name foo, the value is simply just #bean:foo.
-Configuring an AggregationStrategy is required, and is used to merge the incoming Exchange with the existing already
-merged exchanges. At first call the oldExchange parameter is null. On subsequent invocations the oldExchange contains
-the merged exchanges and newExchange is of course the new incoming Exchange.
+The script to execute that creates the bean when using scripting languages.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="aggregationStrategyMethodName" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-This option can be used to explicit declare the method name to use, when using beans as the AggregationStrategy.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="aggregationStrategyMethodAllowNull" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-If this option is false then the aggregate method is not used for the very first aggregation. If this option is true
-then null values is used as the oldExchange (at the very first aggregation), when using beans as the
-AggregationStrategy. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="completionSize" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Number of messages aggregated before the aggregation is complete. This option can be set as either a fixed value or
-using an Expression which allows you to evaluate a size dynamically - will use Integer as result. If both are set Camel
-will fallback to use the fixed value if the Expression result was null or 0.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="completionInterval" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-A repeating period in millis by which the aggregator will complete all current aggregated exchanges. Camel has a
-background task which is triggered every period. You cannot use this option together with completionTimeout, only one of
-them can be used.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="completionTimeout" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Time in millis that an aggregated exchange should be inactive before its complete (timeout). This option can be set as
-either a fixed value or using an Expression which allows you to evaluate a timeout dynamically - will use Long as
-result. If both are set Camel will fallback to use the fixed value if the Expression result was null or 0. You cannot
-use this option together with completionInterval, only one of the two can be used. By default the timeout checker runs
-every second, you can use the completionTimeoutCheckerInterval option to configure how frequently to run the checker.
-The timeout is an approximation and there is no guarantee that the a timeout is triggered exactly after the timeout
-value. It is not recommended to use very low timeout values or checker intervals.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="completionTimeoutCheckerInterval" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Interval in millis that is used by the background task that checks for timeouts ( org.apache.camel.TimeoutMap ). By
-default the timeout checker runs every second. The timeout is an approximation and there is no guarantee that the a
-timeout is triggered exactly after the timeout value. It is not recommended to use very low timeout values or checker
-intervals. Default value: 1000
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="completionFromBatchConsumer" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Enables the batch completion mode where we aggregate from a org.apache.camel.BatchConsumer and aggregate the total
-number of exchanges the org.apache.camel.BatchConsumer has reported as total by checking the exchange property
-org.apache.camel.Exchange#BATCH_COMPLETE when its complete. This option cannot be used together with
-discardOnAggregationFailure. Important: When using this option, you should also enable eagerCheckCompletion() to ensure
-the aggregator checks for batch completion on each incoming exchange. Without eager checking, the batch completion
-signal may not be properly detected. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="completionOnNewCorrelationGroup" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Enables completion on all previous groups when a new incoming correlation group. This can for example be used to
-complete groups with same correlation keys when they are in consecutive order. Notice when this is enabled then only 1
-correlation group can be in progress as when a new correlation group starts, then the previous groups is forced
-completed. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="eagerCheckCompletion" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Use eager completion checking which means that the completionPredicate will use the incoming Exchange. As opposed to
-without eager completion checking the completionPredicate will use the aggregated Exchange. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="ignoreInvalidCorrelationKeys" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-If a correlation key cannot be successfully evaluated it will be ignored by logging a DEBUG and then just ignore the
-incoming Exchange. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="closeCorrelationKeyOnCompletion" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Closes a correlation key when its complete. Any late received exchanges which has a correlation key that has been
-closed, it will be defined and a ClosedCorrelationKeyException is thrown.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="discardOnCompletionTimeout" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Discards the aggregated message on completion timeout. This means on timeout the aggregated message is dropped and not
-sent out of the aggregator. Default value: false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="discardOnAggregationFailure" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:element>
+ </xs:sequence>
+ <xs:attribute name="name" type="xs:string" use="required">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Discards the aggregated message when aggregation failed (an exception was thrown from AggregationStrategy . This means
-the partly aggregated message is dropped and not sent out of the aggregator. This option cannot be used together with
-completionFromBatchConsumer. Default value: false
+The name of the bean (bean id).
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="forceCompletionOnStop" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="type" type="xs:string" use="required">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Indicates to complete all current aggregated exchanges when the context is stopped. Default value: false
+The class name (fully qualified) of the bean.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="completeAllOnStop" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="initMethod" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Indicates to wait to complete all current and partial (pending) aggregated exchanges when the context is stopped. This
-also means that we will wait for all pending exchanges which are stored in the aggregation repository to complete so the
-repository is empty before we can stop. You may want to enable this when using the memory based aggregation repository
-that is memory based only, and do not store data on disk. When this option is enabled, then the aggregator is waiting to
-complete all those exchanges before its stopped, when stopping CamelContext or the route using it. Default value: false
+The name of the custom initialization method to invoke after setting bean properties. The method must have no arguments,
+but may throw any exception.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="expressionSubElementDefinition">
- <xs:choice>
- <xs:element ref="tns:expressionDefinition"/>
- <xs:element ref="tns:csimple"/>
- <xs:element ref="tns:constant"/>
- <xs:element ref="tns:datasonnet"/>
- <xs:element ref="tns:exchangeProperty"/>
- <xs:element ref="tns:groovy"/>
- <xs:element ref="tns:header"/>
- <xs:element ref="tns:hl7terser"/>
- <xs:element ref="tns:java"/>
- <xs:element ref="tns:js"/>
- <xs:element ref="tns:joor"/>
- <xs:element ref="tns:jq"/>
- <xs:element ref="tns:jsonpath"/>
- <xs:element ref="tns:language"/>
- <xs:element ref="tns:method"/>
- <xs:element ref="tns:mvel"/>
- <xs:element ref="tns:ognl"/>
- <xs:element ref="tns:python"/>
- <xs:element ref="tns:ref"/>
- <xs:element ref="tns:simple"/>
- <xs:element ref="tns:spel"/>
- <xs:element ref="tns:tokenize"/>
- <xs:element ref="tns:variable"/>
- <xs:element ref="tns:wasm"/>
- <xs:element ref="tns:xtokenize"/>
- <xs:element ref="tns:xpath"/>
- <xs:element ref="tns:xquery"/>
- </xs:choice>
- </xs:complexType>
- <xs:complexType name="expression">
- <xs:simpleContent>
- <xs:extension base="xs:string">
- <xs:attribute name="id" type="xs:ID">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="destroyMethod" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Sets the id of this node.
+The name of the custom destroy method to invoke on bean shutdown, such as when Camel is shutting down. The method must
+have no arguments, but may throw any exception.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="trim" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="factoryMethod" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
<![CDATA[
-Whether to trim the source code to remove leading and trailing whitespaces and line breaks. For example when using DSLs
-where the source will span across multiple lines and there may be additional line breaks at both the beginning and end.
-Default value: true
+Name of method to invoke when creating the bean via a factory bean.
]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:simpleContent>
- </xs:complexType>
- <xs:complexType name="optimisticLockRetryPolicyDefinition">
- <xs:sequence/>
- <xs:attribute name="maximumRetries" type="xs:string">
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="factoryBean" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum number of retries.
+Name of factory bean (bean id) to use for creating the bean.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="retryDelay" type="xs:string">
+ <xs:attribute name="builderClass" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the delay in millis between retries. Default value: 50
+Fully qualified class name of builder class to use for creating and configuring the bean. The builder will use the
+properties values to configure the bean.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="maximumRetryDelay" type="xs:string">
+ <xs:attribute name="builderMethod" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the upper value of retry in millis between retries, when using exponential or random backoff. Default value: 1000
+Name of method when using builder class. This method is invoked after configuring to create the actual bean. This method
+is often named build (used by default). Default value: build
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="exponentialBackOff" type="xs:string">
+ <xs:attribute name="scriptLanguage" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Enable exponential backoff. Default value: true
+The script language to use when using inlined script for creating the bean, such as groovy, java, javascript etc.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="randomBackOff" type="xs:string">
+ <xs:attribute name="scriptPropertyPlaceholders" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Enables random backoff. Default value: false
+Whether the script should support using Camel property placeholder syntax {{ }}. Default value: true
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:complexType>
- <xs:complexType name="beanDefinition">
- <xs:complexContent>
- <xs:extension base="tns:noOutputDefinition">
- <xs:sequence/>
- <xs:attribute name="ref" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Sets a reference to an existing bean to use, which is looked up from the registry.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="method" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Sets the method name on the bean to use.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="beanType" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Sets the class name (fully qualified) of the bean to use.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="scope" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the
-lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same
-time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you
-want to store state on a bean while processing a request and you want to call the same bean instance multiple times
-while processing the request. The bean does not have to be thread-safe as the instance is only called from the same
-request. When using prototype scope, then the bean will be looked up or created per call. However in case of lookup then
-this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act
-as either singleton or prototype scope. So when using prototype scope then this depends on the bean registry
-implementation. Default value: Singleton
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType abstract="true" name="noOutputDefinition">
- <xs:complexContent>
- <xs:extension base="tns:processorDefinition">
- <xs:sequence/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="beanFactoryDefinition">
- <xs:sequence>
- <xs:element minOccurs="0" name="constructors" type="tns:beanConstructorsDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Optional constructor arguments for creating the bean. Arguments correspond to specific index of the constructor argument
-list, starting from zero.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element minOccurs="0" name="properties" type="tns:beanPropertiesDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Optional properties to set on the created bean.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element minOccurs="0" name="script" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The script to execute that creates the bean when using scripting languages. If the script use the prefix resource: such
-as resource:classpath:com/foo/myscript.groovy, resource:file:/var/myscript.groovy, then its loaded from the external
-resource.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- </xs:sequence>
- <xs:attribute name="name" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The name of the bean (bean id).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="type" type="xs:string" use="required">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The class name (fully qualified) of the bean.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="initMethod" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The name of the custom initialization method to invoke after setting bean properties. The method must have no arguments,
-but may throw any exception.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="destroyMethod" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The name of the custom destroy method to invoke on bean shutdown, such as when Camel is shutting down. The method must
-have no arguments, but may throw any exception.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="factoryMethod" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Name of method to invoke when creating the bean via a factory bean.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="factoryBean" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Name of factory bean (bean id) to use for creating the bean.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="builderClass" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Fully qualified class name of builder class to use for creating and configuring the bean. The builder will use the
-properties values to configure the bean.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="builderMethod" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Name of method when using builder class. This method is invoked after configuring to create the actual bean. This method
-is often named build (used by default). Default value: build
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="scriptLanguage" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The script language to use when using inlined script for creating the bean, such as groovy, java, javascript etc.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="scriptPropertyPlaceholders" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Whether the script should support using Camel property placeholder syntax {{ }}. Default value: true
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:complexType>
- <xs:complexType name="beanConstructorsDefinition">
- <xs:sequence>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="constructor" type="tns:beanConstructorDefinition"/>
- </xs:sequence>
- </xs:complexType>
- <xs:complexType name="beanConstructorDefinition">
- <xs:sequence/>
- <xs:attribute name="index" type="xs:int"/>
- <xs:attribute name="value" type="xs:string" use="required"/>
- </xs:complexType>
- <xs:complexType name="beanPropertiesDefinition">
- <xs:sequence>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="property" type="tns:beanPropertyDefinition"/>
- </xs:sequence>
- </xs:complexType>
- <xs:complexType name="beanPropertyDefinition">
- <xs:sequence>
- <xs:element minOccurs="0" name="properties" type="tns:beanPropertiesDefinition"/>
- </xs:sequence>
- <xs:attribute name="key" type="xs:string"/>
- <xs:attribute name="value" type="xs:string"/>
- </xs:complexType>
- <xs:complexType name="catchDefinition">
+ <xs:complexType name="beanConstructorsDefinition">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="constructor" type="tns:beanConstructorDefinition"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="beanConstructorDefinition">
+ <xs:sequence/>
+ <xs:attribute name="index" type="xs:int"/>
+ <xs:attribute name="value" type="xs:string" use="required"/>
+ </xs:complexType>
+ <xs:complexType name="beanPropertiesDefinition">
+ <xs:sequence>
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="property" type="tns:beanPropertyDefinition"/>
+ </xs:sequence>
+ </xs:complexType>
+ <xs:complexType name="beanPropertyDefinition">
+ <xs:sequence>
+ <xs:element minOccurs="0" name="properties" type="tns:beanPropertiesDefinition"/>
+ </xs:sequence>
+ <xs:attribute name="key" type="xs:string"/>
+ <xs:attribute name="value" type="xs:string"/>
+ </xs:complexType>
+ <xs:complexType name="catchDefinition">
<xs:complexContent>
<xs:extension base="tns:output">
<xs:sequence>
@@ -4403,13 +3912,14 @@ Whether the script should support using Camel property placeholder syntax {{ }}.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The exception(s) to catch.
+The exception class names (fully qualified) to catch.
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" ref="tns:onWhen"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -4480,7 +3990,6 @@ The exception(s) to catch.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -4498,6 +4007,7 @@ The exception(s) to catch.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -4532,8 +4042,8 @@ The exception(s) to catch.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Indicates whether this Choice EIP is in precondition mode or not. If so its branches (when/otherwise) are evaluated
-during startup to keep at runtime only the branch that matched. Default value: false
+If enabled then the choice is evaluated at route initialization time (precondition). Only when predicates with property
+placeholders or simple expressions using only property placeholders are supported. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -4554,6 +4064,7 @@ during startup to keep at runtime only the branch that matched. Default value: f
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -4575,6 +4086,7 @@ during startup to keep at runtime only the branch that matched. Default value: f
<xs:element ref="tns:xquery"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -4645,7 +4157,6 @@ during startup to keep at runtime only the branch that matched. Default value: f
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="disabled" type="xs:string">
@@ -4665,6 +4176,7 @@ Disables this EIP from the route. Default value: false
<xs:extension base="tns:optionalIdentifiedDefinition">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -4735,7 +4247,6 @@ Disables this EIP from the route. Default value: false
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="disabled" type="xs:string">
@@ -4757,6 +4268,7 @@ Disables this EIP from the route. Default value: false
<xs:element minOccurs="0" ref="tns:resilience4jConfiguration"/>
<xs:element minOccurs="0" ref="tns:faultToleranceConfiguration"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -4827,7 +4339,6 @@ Disables this EIP from the route. Default value: false
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
<xs:element minOccurs="0" ref="tns:onFallback"/>
</xs:sequence>
@@ -4835,8 +4346,7 @@ Disables this EIP from the route. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a circuit breaker configuration (such as resillience4j, or microprofile-fault-tolerance) to use for
-configuring the circuit breaker EIP.
+Refers to a circuit breaker configuration to use for configuring the circuit breaker EIP.
]]>
</xs:documentation>
</xs:annotation>
@@ -4845,10 +4355,8 @@ configuring the circuit breaker EIP.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To turn on or off Camel error handling during circuit breaker. If this is enabled then Camel error handler will first
-trigger if there is an error in the circuit breaker, which allows to let Camel handle redeliveries. If all attempts is
-failed, then after the circuit breaker is finished, then Camel error handler can handle the error as well such as the
-dead letter channel. By default, Camel error handler is turned off. Default value: false
+Whether to inherit Camel error handling during circuit breaker. By default, Camel error handler is turned off. Default
+value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -4882,7 +4390,7 @@ or inheriting from one of the list counts as a failure, unless explicitly ignore
<xs:documentation xml:lang="en">
<![CDATA[
Configure a list of exceptions that are ignored and neither count as a failure nor success. Any exception matching or
-inheriting from one of the list will not count as a failure nor success, even if the exceptions is part of
+inheriting from one of the list will not count as a failure nor success, even if the exception is part of
recordExceptions.
]]>
</xs:documentation>
@@ -4914,8 +4422,7 @@ registry.
<xs:documentation xml:lang="en">
<![CDATA[
Configures the failure rate threshold in percentage. If the failure rate is equal or greater than the threshold the
-CircuitBreaker transitions to open and starts short-circuiting calls. The threshold must be greater than 0 and not
-greater than 100. Default value is 50 percentage. Default value: 50
+CircuitBreaker transitions to open and starts short-circuiting calls. Default value: 50
]]>
</xs:documentation>
</xs:annotation>
@@ -4924,8 +4431,7 @@ greater than 100. Default value is 50 percentage. Default value: 50
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Configures the number of permitted calls when the CircuitBreaker is half open. The size must be greater than 0. Default
-size is 10. Default value: 10
+Configures the number of permitted calls when the CircuitBreaker is half open. Default value: 10
]]>
</xs:documentation>
</xs:annotation>
@@ -4934,10 +4440,8 @@ size is 10. Default value: 10
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to throw io.github.resilience4j.circuitbreaker.CallNotPermittedException when the call is rejected due circuit
-breaker is half open (and was not attempted but rejected immediately) or open (always rejected). This option is only in
-use when there is NOT a fallback configured on the circuit breaker. When there is a fallback then the fallback is always
-executed and CallNotPermittedException is not thrown. Default value: false
+Whether to throw io.github.resilience4j.circuitbreaker.CallNotPermittedException when the call is rejected because the
+circuit breaker is half open or open. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -4947,12 +4451,7 @@ executed and CallNotPermittedException is not thrown. Default value: false
<xs:documentation xml:lang="en">
<![CDATA[
Configures the size of the sliding window which is used to record the outcome of calls when the CircuitBreaker is
-closed. slidingWindowSize configures the size of the sliding window. Sliding window can either be count-based or
-time-based. If slidingWindowType is COUNT_BASED, the last slidingWindowSize calls are recorded and aggregated. If
-slidingWindowType is TIME_BASED, the calls of the last slidingWindowSize seconds are recorded and aggregated. The
-slidingWindowSize must be greater than 0. The minimumNumberOfCalls must be greater than 0. If the slidingWindowType is
-COUNT_BASED, the minimumNumberOfCalls cannot be greater than slidingWindowSize . If the slidingWindowType is TIME_BASED,
-you can pick whatever you want. Default slidingWindowSize is 100. Default value: 100
+closed. Sliding window can either be count-based or time-based. Default value: 100
]]>
</xs:documentation>
</xs:annotation>
@@ -4962,10 +4461,18 @@ you can pick whatever you want. Default slidingWindowSize is 100. Default value:
<xs:documentation xml:lang="en">
<![CDATA[
Configures the type of the sliding window which is used to record the outcome of calls when the CircuitBreaker is
-closed. Sliding window can either be count-based or time-based. If slidingWindowType is COUNT_BASED, the last
-slidingWindowSize calls are recorded and aggregated. If slidingWindowType is TIME_BASED, the calls of the last
-slidingWindowSize seconds are recorded and aggregated. Default slidingWindowType is COUNT_BASED. Default value:
-COUNT_BASED
+closed. Sliding window can either be count-based or time-based. Default value: COUNT_BASED
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="slidingWindowSynchronizationStrategy" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Configures the synchronization strategy for the sliding window. LOCK_FREE uses a CAS-based lock-free algorithm for
+better performance under high concurrency. SYNCHRONIZED uses blocking locks with lower memory allocation. Default value:
+SYNCHRONIZED
]]>
</xs:documentation>
</xs:annotation>
@@ -4975,9 +4482,7 @@ COUNT_BASED
<xs:documentation xml:lang="en">
<![CDATA[
Configures the minimum number of calls which are required (per sliding window period) before the CircuitBreaker can
-calculate the error rate. For example, if minimumNumberOfCalls is 10, then at least 10 calls must be recorded, before
-the failure rate can be calculated. If only 9 calls have been recorded the CircuitBreaker will not transition to open
-even if all 9 calls have failed. Default minimumNumberOfCalls is 100. Default value: 100
+calculate the error rate. Default value: 100
]]>
</xs:documentation>
</xs:annotation>
@@ -4987,8 +4492,7 @@ even if all 9 calls have failed. Default minimumNumberOfCalls is 100. Default va
<xs:documentation xml:lang="en">
<![CDATA[
Enables writable stack traces. When set to false, Exception.getStackTrace returns a zero length array. This may be used
-to reduce log spam when the circuit breaker is open as the cause of the exceptions is already known (the circuit breaker
-is short-circuiting calls). Default value: true
+to reduce log spam when the circuit breaker is open. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -4997,8 +4501,8 @@ is short-circuiting calls). Default value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Configures the wait duration (in seconds) which specifies how long the CircuitBreaker should stay open, before it
-switches to half open. Default value is 60 seconds. Default value: 60
+Configures the wait duration which specifies how long the CircuitBreaker should stay open, before it switches to half
+open. The default is 60 seconds. Default value: 60000
]]>
</xs:documentation>
</xs:annotation>
@@ -5009,6 +4513,17 @@ switches to half open. Default value is 60 seconds. Default value: 60
<![CDATA[
Enables automatic transition from OPEN to HALF_OPEN state once the waitDurationInOpenState has passed. Default value:
false
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="maxWaitDurationInHalfOpenState" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Configures the maximum wait duration which controls how long the CircuitBreaker should stay in Half Open state, before
+it switches to open. Value 0 means circuit breaker will wait in half open state until all permitted calls have been
+completed. Default value: 0
]]>
</xs:documentation>
</xs:annotation>
@@ -5018,10 +4533,8 @@ false
<xs:documentation xml:lang="en">
<![CDATA[
Configures a threshold in percentage. The CircuitBreaker considers a call as slow when the call duration is greater than
-slowCallDurationThreshold Duration. When the percentage of slow calls is equal or greater the threshold, the
-CircuitBreaker transitions to open and starts short-circuiting calls. The threshold must be greater than 0 and not
-greater than 100. Default value is 100 percentage which means that all recorded calls must be slower than
-slowCallDurationThreshold. Default value: 100
+slowCallDurationThreshold. When the percentage of slow calls is equal or greater the threshold, the CircuitBreaker
+transitions to open and starts short-circuiting calls. Default value: 100
]]>
</xs:documentation>
</xs:annotation>
@@ -5030,8 +4543,8 @@ slowCallDurationThreshold. Default value: 100
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Configures the duration threshold (seconds) above which calls are considered as slow and increase the slow calls
-percentage. Default value is 60 seconds. Default value: 60
+Configures the duration threshold above which calls are considered as slow and increase the slow calls percentage. The
+default is 60 seconds. Default value: 60000
]]>
</xs:documentation>
</xs:annotation>
@@ -5040,7 +4553,7 @@ percentage. Default value is 60 seconds. Default value: 60
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether bulkhead is enabled or not on the circuit breaker. Default is false. Default value: false
+Whether bulkhead is enabled or not on the circuit breaker. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5058,11 +4571,31 @@ Configures the max amount of concurrent calls the bulkhead will support. Default
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Configures a maximum amount of time which the calling thread will wait to enter the bulkhead. If bulkhead has space
-available, entry is guaranteed and immediate. If bulkhead is full, calling threads will contest for space, if it becomes
-available. maxWaitDuration can be set to 0. Note: for threads running on an event-loop or equivalent (rx computation
-pool, etc), setting maxWaitDuration to 0 is highly recommended. Blocking an event-loop thread will most likely have a
-negative effect on application throughput. Default value: 0
+Configures a maximum amount of time which the calling thread will wait to enter the bulkhead. The default is 0 (no
+waiting). Default value: 0
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="bulkheadFairCallHandlingEnabled" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Configures whether the bulkhead uses a fair calling strategy. When enabled (default), a fair strategy guarantees the
+order of incoming requests (FIFO). When disabled, no ordering is guaranteed and may improve throughput. Default value:
+true
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="asynchronous" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Whether to use asynchronous (non-blocking) processing with CompletionStage-based circuit breaker decorators. When
+enabled, the circuit breaker releases the caller thread immediately and completes processing asynchronously. This is
+most valuable when the downstream processor supports asynchronous processing (e.g. Netty HTTP, Kafka). When used with
+timeout, the timeoutExecutorService must be a ScheduledExecutorService. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5071,7 +4604,7 @@ negative effect on application throughput. Default value: 0
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether timeout is enabled or not on the circuit breaker. Default is false. Default value: false
+Whether timeout is enabled or not on the circuit breaker. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5080,7 +4613,7 @@ Whether timeout is enabled or not on the circuit breaker. Default is false. Defa
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-References to a custom thread pool to use when timeout is enabled (uses ForkJoinPool#commonPool() by default).
+References to a custom thread pool to use when timeout is enabled (uses ForkJoinPool.commonPool() by default).
]]>
</xs:documentation>
</xs:annotation>
@@ -5107,7 +4640,8 @@ Configures whether cancel is called on the running future. Defaults to true. Def
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to enable collecting statistics using Micrometer. This requires adding camel-resilience4j-micrometer JAR to the
+Whether to enable collecting statistics using Micrometer for all circuit breaker instances. This is a global setting
+(configure via camel.resilience4j.micrometerEnabled=true) and requires adding camel-resilience4j-micrometer JAR to the
classpath. Default value: false
]]>
</xs:documentation>
@@ -5169,8 +4703,7 @@ Controls the size of the rolling window used when the circuit breaker is closed.
<xs:documentation xml:lang="en">
<![CDATA[
Configures the failure rate threshold in percentage. If the failure rate is equal or greater than the threshold the
-CircuitBreaker transitions to open and starts short-circuiting calls. The threshold must be greater than 0 and not
-greater than 100. Default value is 50 percentage. Default value: 50
+CircuitBreaker transitions to open and starts short-circuiting calls. Default value: 50
]]>
</xs:documentation>
</xs:annotation>
@@ -5179,7 +4712,7 @@ greater than 100. Default value is 50 percentage. Default value: 50
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether timeout is enabled or not on the circuit breaker. Default is false. Default value: false
+Whether timeout is enabled or not on the circuit breaker. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5189,15 +4722,6 @@ Whether timeout is enabled or not on the circuit breaker. Default is false. Defa
<xs:documentation xml:lang="en">
<![CDATA[
Configures the thread execution timeout. Default value is 1 second. Default value: 1000
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="timeoutPoolSize" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Configures the pool size of the thread pool when timeout is enabled. Default value is 10. Default value: 10
]]>
</xs:documentation>
</xs:annotation>
@@ -5206,7 +4730,7 @@ Configures the pool size of the thread pool when timeout is enabled. Default val
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether bulkhead is enabled or not on the circuit breaker. Default is false. Default value: false
+Whether bulkhead is enabled or not on the circuit breaker. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5246,6 +4770,7 @@ References a custom thread pool to use when offloading a guarded action to anoth
<xs:extension base="tns:optionalIdentifiedDefinition">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -5316,17 +4841,14 @@ References a custom thread pool to use when offloading a guarded action to anoth
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="fallbackViaNetwork" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether the fallback goes over the network. If the fallback will go over the network it is another possible point of
-failure. It is important to execute the fallback command on a separate thread-pool, otherwise if the main command were
-to become latent and fill the thread-pool this would prevent the fallback from running if the two commands share the
-same pool. Default value: false
+Deprecated: Whether the fallback goes over the network. If so, the fallback is executed on a separate thread-pool to
+avoid exhausting the main thread-pool. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5342,10 +4864,8 @@ same pool. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The claim check operation to use. The following operations are supported: Get - Gets (does not remove) the claim check
-by the given key. GetAndRemove - Gets and removes the claim check by the given key. Set - Sets a new (will override if
-key already exists) claim check with the given key. Push - Sets a new claim check on the stack (does not use key). Pop -
-Gets the latest claim check from the stack (does not use key).
+The claim check operation to use. Get=retrieve, GetAndRemove=retrieve and remove, Set=store with key, Push=store on
+stack, Pop=retrieve from stack.
]]>
</xs:documentation>
</xs:annotation>
@@ -5354,7 +4874,7 @@ Gets the latest claim check from the stack (does not use key).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a specific key for claim check id (for dynamic keys use simple language syntax as the key).
+The unique claim check key to use for Get, GetAndRemove, and Set operations.
]]>
</xs:documentation>
</xs:annotation>
@@ -5363,16 +4883,8 @@ To use a specific key for claim check id (for dynamic keys use simple language s
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Specify a filter to control what data gets merged data back from the claim check repository. The following syntax is
-supported: body - to aggregate the message body attachments - to aggregate all the message attachments headers - to
-aggregate all the message headers header:pattern - to aggregate all the message headers that matches the pattern. The
-following pattern rules are applied in this order: exact match, returns true wildcard match (pattern ends with a and the
-name starts with the pattern), returns true regular expression match, returns true otherwise returns false You can
-specify multiple rules separated by comma. For example, the following includes the message body and all headers starting
-with foo: body,header:foo. The syntax supports the following prefixes which can be used to specify include,exclude, or
-remove - to include (which is the default mode) - - to exclude (exclude takes precedence over include) -- - to remove
-(remove takes precedence) For example to exclude a header name foo, and remove all headers starting with bar,
--header:foo,--headers:bar Note you cannot have both include and exclude header:pattern at the same time.
+Specifies a filter to control what data gets merged back when using Get or Pop operations. Use body, headers,
+header:pattern to include only matching data.
]]>
</xs:documentation>
</xs:annotation>
@@ -5381,8 +4893,7 @@ remove - to include (which is the default mode) - - to exclude (exclude takes pr
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom AggregationStrategy instead of the default implementation. Notice you cannot use both custom aggregation
-strategy and configure data at the same time.
+Reference to a custom AggregationStrategy to use for merging data back from the claim check repository.
]]>
</xs:documentation>
</xs:annotation>
@@ -5391,7 +4902,7 @@ strategy and configure data at the same time.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-This option can be used to explicit declare the method name to use, when using POJOs as the AggregationStrategy.
+The method name to use when using a POJO as the AggregationStrategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -5427,7 +4938,7 @@ Include finding route builder from these java package names.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to include non-singleton beans (prototypes) By default only singleton beans is included in the context scan.
+Whether to include non-singleton beans (prototypes). By default only singleton beans are included in the context scan.
Default value: false
]]>
</xs:documentation>
@@ -5451,9 +4962,8 @@ The java type to convert to.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-When mandatory then the conversion must return a value (cannot be null), if this is not possible then
-NoTypeConversionAvailableException is thrown. Setting this to false could mean conversion is not possible and the value
-is null. Default value: true
+Whether the conversion is mandatory. If mandatory and conversion is not possible, a NoTypeConversionAvailableException
+is thrown. Setting this to false means null may be returned if conversion is not possible. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -5478,8 +4988,7 @@ To use a specific charset when converting.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of message header to convert its value The simple language can be used to define a dynamic evaluated header name to
-be used. Otherwise a constant name will be used.
+Name of message header to convert its value. The simple language can be used to define a dynamic evaluated header name.
]]>
</xs:documentation>
</xs:annotation>
@@ -5497,9 +5006,7 @@ The java type to convert to.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use another header to store the result. By default, the result is stored in the same header. This option allows to
-use another header. The simple language can be used to define a dynamic evaluated header name to be used. Otherwise a
-constant name will be used.
+To use another header to store the result. By default, the result is stored in the same header.
]]>
</xs:documentation>
</xs:annotation>
@@ -5508,9 +5015,8 @@ constant name will be used.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-When mandatory then the conversion must return a value (cannot be null), if this is not possible then
-NoTypeConversionAvailableException is thrown. Setting this to false could mean conversion is not possible and the value
-is null. Default value: true
+Whether the conversion is mandatory. If mandatory and conversion is not possible, a NoTypeConversionAvailableException
+is thrown. Setting this to false means null may be returned if conversion is not possible. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -5535,8 +5041,7 @@ To use a specific charset when converting.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of variable to convert its value The simple language can be used to define a dynamic evaluated header name to be
-used. Otherwise a constant name will be used.
+Name of variable to convert its value. The simple language can be used to define a dynamic evaluated variable name.
]]>
</xs:documentation>
</xs:annotation>
@@ -5554,9 +5059,7 @@ The java type to convert to.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use another variable to store the result. By default, the result is stored in the same variable. This option allows
-to use another variable. The simple language can be used to define a dynamic evaluated variable name to be used.
-Otherwise a constant name will be used.
+To use another variable to store the result. By default, the result is stored in the same variable.
]]>
</xs:documentation>
</xs:annotation>
@@ -5565,9 +5068,8 @@ Otherwise a constant name will be used.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-When mandatory then the conversion must return a value (cannot be null), if this is not possible then
-NoTypeConversionAvailableException is thrown. Setting this to false could mean conversion is not possible and the value
-is null. Default value: true
+Whether the conversion is mandatory. If mandatory and conversion is not possible, a NoTypeConversionAvailableException
+is thrown. Setting this to false means null may be returned if conversion is not possible. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -5603,6 +5105,7 @@ To use a specific charset when converting.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -5636,8 +5139,7 @@ Enables asynchronous delay which means the thread will not block while delaying.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the caller should run the task when it was rejected by the thread pool. Is by default true. Default
-value: true
+Whether or not the caller should run the task when it was rejected by the thread pool. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -5646,7 +5148,7 @@ value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom Thread Pool if asyncDelay has been enabled.
+To use a custom thread pool if asyncDelay has been enabled.
]]>
</xs:documentation>
</xs:annotation>
@@ -5666,6 +5168,7 @@ To use a custom Thread Pool if asyncDelay has been enabled.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -5690,7 +5193,8 @@ To use a custom Thread Pool if asyncDelay has been enabled.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the uri delimiter to use. Default value: ,
+The delimiter used to separate endpoint URIs when the expression returns multiple endpoints. Default is comma. Default
+value: ,
]]>
</xs:documentation>
</xs:annotation>
@@ -5699,7 +5203,7 @@ Sets the uri delimiter to use. Default value: ,
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Ignore the invalidate endpoint exception when try to create a producer with that endpoint. Default value: false
+If enabled then invalid endpoint URIs are ignored and logged instead of throwing an exception. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5708,15 +5212,19 @@ Ignore the invalidate endpoint exception when try to create a producer with that
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum size used by the org.apache.camel.spi.ProducerCache which is used to cache and reuse producers when
-using this dynamic router, when uris are reused. Beware that when using dynamic endpoints then it affects how well the
-cache can be utilized. If each dynamic endpoint is unique then its best to turn off caching by setting this to -1, which
-allows Camel to not cache both the producers and endpoints; they are regarded as prototype scoped and will be stopped
-and discarded after use. This reduces memory usage as otherwise producers/endpoints are stored in memory in the caches.
-However if there are a high degree of dynamic endpoints that have been used before, then it can benefit to use the cache
-to reuse both producers and endpoints and therefore the cache size can be set accordingly or rely on the default size
-(1000). If there is a mix of unique and used before dynamic endpoints, then setting a reasonable cache size can help
-reduce memory usage to avoid storing too many non frequent used producers.
+Configures the cache size for ProducerCache which caches producers for reuse. The default cache size is 1000. Set to -1
+to turn off caching.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="allowedSchemes" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets an optional comma-separated allow-list of component schemes that the dynamic recipient may resolve to (e.g.
+http,https). When set, a dynamic endpoint whose scheme is not in the list is rejected. This is a defence-in-depth
+restriction, useful for low-code / Kamelet deployments; by default (unset) any scheme is allowed.
]]>
</xs:documentation>
</xs:annotation>
@@ -5736,6 +5244,7 @@ reduce memory usage to avoid storing too many non frequent used producers.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -5760,9 +5269,8 @@ reduce memory usage to avoid storing too many non frequent used producers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
-user data and to easily control what data to use for sending and receiving. Important: When using receive variable then
-the received body is stored only in this variable and not on the current message.
+To use a variable as the source for the message body to send. When using send variable then the message body is taken
+from this variable instead of the current message, however the headers from the message will still be used as well.
]]>
</xs:documentation>
</xs:annotation>
@@ -5771,10 +5279,8 @@ the received body is stored only in this variable and not on the current message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to
-easily control what data to use for sending and receiving. Important: When using send variable then the message body is
-taken from this variable instead of the current message, however the headers from the message will still be used as
-well. In other words, the variable is used instead of the message body, but everything else is as usual.
+To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -5793,7 +5299,7 @@ default Camel will use the reply from the external service as outgoing message.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-This option can be used to explicit declare the method name to use, when using POJOs as the AggregationStrategy.
+This option can be used to explicitly declare the method name to use, when using POJOs as the AggregationStrategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -5814,8 +5320,7 @@ then null values is used as the oldExchange (when no data to enrich), when using
<![CDATA[
If this option is false then the aggregate method is not used if there was an exception thrown while trying to retrieve
the data to enrich from the resource. Setting this option to true allows end users to control what to do if there was an
-exception in the aggregate method. For example to suppress the exception or set a custom message body etc. Default
-value: false
+exception in the aggregate method. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5824,9 +5329,9 @@ value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Shares the org.apache.camel.spi.UnitOfWork with the parent and the resource exchange. Enrich will by default not share
-unit of work between the parent exchange and the resource exchange. This means the resource exchange has its own
-individual unit of work. Default value: false
+Shares the UnitOfWork with the parent and the resource exchange. Enrich will by default not share unit of work between
+the parent exchange and the resource exchange. This means the resource exchange has its own individual unit of work.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5835,15 +5340,8 @@ individual unit of work. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum size used by the org.apache.camel.spi.ProducerCache which is used to cache and reuse producer when uris
-are reused. Beware that when using dynamic endpoints then it affects how well the cache can be utilized. If each dynamic
-endpoint is unique then its best to turn off caching by setting this to -1, which allows Camel to not cache both the
-producers and endpoints; they are regarded as prototype scoped and will be stopped and discarded after use. This reduces
-memory usage as otherwise producers/endpoints are stored in memory in the caches. However if there are a high degree of
-dynamic endpoints that have been used before, then it can benefit to use the cache to reuse both producers and endpoints
-and therefore the cache size can be set accordingly or rely on the default size (1000). If there is a mix of unique and
-used before dynamic endpoints, then setting a reasonable cache size can help reduce memory usage to avoid storing too
-many non frequent used producers.
+Sets the maximum size used by the ProducerCache which is used to cache and reuse producers when uris are reused. Use 0
+for default cache size, or -1 to turn cache off.
]]>
</xs:documentation>
</xs:annotation>
@@ -5852,7 +5350,7 @@ many non frequent used producers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Ignore the invalidate endpoint exception when try to create a producer with that endpoint. Default value: false
+Whether to ignore an invalid endpoint URI when trying to create a producer with that endpoint. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5861,7 +5359,7 @@ Ignore the invalidate endpoint exception when try to create a producer with that
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to allow components to optimise enricher if they are org.apache.camel.spi.SendDynamicAware. Default value: true
+Whether to allow components to optimise enricher if they are SendDynamicAware. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -5871,6 +5369,17 @@ Whether to allow components to optimise enricher if they are org.apache.camel.sp
<xs:documentation xml:lang="en">
<![CDATA[
Whether to auto startup components when enricher is starting up. Default value: true
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="allowedSchemes" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets an optional comma-separated allow-list of component schemes that the dynamic recipient may resolve to (e.g.
+http,https). When set, a dynamic endpoint whose scheme is not in the list is rejected. This is a defence-in-depth
+restriction, useful for low-code / Kamelet deployments; by default (unset) any scheme is allowed.
]]>
</xs:documentation>
</xs:annotation>
@@ -5902,7 +5411,8 @@ Whether to auto startup components when enricher is starting up. Default value:
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The dead letter endpoint uri for the Dead Letter error handler.
+The endpoint URI where failed exchanges are sent after all redelivery attempts have been exhausted (the dead letter
+queue).
]]>
</xs:documentation>
</xs:annotation>
@@ -5911,13 +5421,9 @@ The dead letter endpoint uri for the Dead Letter error handler.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether the dead letter channel should handle (and ignore) any new exception that may been thrown during sending the
-message to the dead letter endpoint. The default value is true which means any such kind of exception is handled and
-ignored. Set this to false to let the exception be propagated back on the org.apache.camel.Exchange . This can be used
-in situations where you use transactions, and want to use Camel's dead letter channel to deal with exceptions during
-routing, but if the dead letter channel itself fails because of a new exception being thrown, then by setting this to
-false the new exceptions is propagated back and set on the org.apache.camel.Exchange , which allows the transaction to
-detect the exception, and rollback. Default value: true
+Whether the dead letter channel should handle (and ignore) any new exception thrown while sending the exchange to the
+dead letter endpoint. Set to false to propagate the new exception back, which is useful with transactions so the
+transaction can detect the failure and rollback. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -5935,30 +5441,8 @@ detect the exception, and rollback. Default value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will use the original input org.apache.camel.Message (original body and headers) when an org.apache.camel.Exchange is
-moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the
-org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN
-message we use the original IN message instead. This allows you to store the original input in the dead letter queue
-instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and
-then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the
-org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send
-the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that
-the former includes both the original body and headers, where as the latter only includes the original body. You can use
-the latter to enrich the message with custom headers and include the original message body. The former wont let you do
-this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and
-useOriginalBody. The original input message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route),
-to ensure the body can be read when the original message is being used later. If the body is converted to
-org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the
-org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not
-be able to re-read when accessed later. Important: The original input means the input message that are bounded by the
-current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are
-connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or
-HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also
-some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their
-sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine
-with the parent unit of work in regard to error handling and therefore use the parent original message. By default this
-feature is off. Default value: false
+If enabled, uses the original input message (body and headers) when the exchange is moved to the dead letter queue after
+all redelivery attempts have been exhausted. Cannot be used together with useOriginalBody. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5967,30 +5451,9 @@ feature is off. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will use the original input org.apache.camel.Message body (original body only) when an org.apache.camel.Exchange is
-moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the
-org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN
-message we use the original IN message instead. This allows you to store the original input in the dead letter queue
-instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and
-then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the
-org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send
-the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that
-the former includes both the original body and headers, where as the latter only includes the original body. You can use
-the latter to enrich the message with custom headers and include the original message body. The former wont let you do
-this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and
-useOriginalBody. The original input message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route),
-to ensure the body can be read when the original message is being used later. If the body is converted to
-org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the
-org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not
-be able to re-read when accessed later. Important: The original input means the input message that are bounded by the
-current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are
-connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or
-HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also
-some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their
-sub-route (eg the splitted message); however these EIPs have an option named shareUnitOfWork which allows to combine
-with the parent unit of work in regard to error handling and therefore use the parent original message. By default this
-feature is off. Default value: false
+If enabled, uses the original input message body (but not headers) when the exchange is moved to the dead letter queue
+after all redelivery attempts have been exhausted. This allows enriching the message with custom headers while keeping
+the original body. Cannot be used together with useOriginalMessage. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -5999,7 +5462,7 @@ feature is off. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a RedeliveryPolicy to be used for redelivery settings.
+Sets a reference to a redelivery policy to lookup in the registry to be used.
]]>
</xs:documentation>
</xs:annotation>
@@ -6008,7 +5471,7 @@ Sets a reference to a RedeliveryPolicy to be used for redelivery settings.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-References to a logger to use as logger for the error handler.
+Sets a reference to a logger to use for logging error handler activity.
]]>
</xs:documentation>
</xs:annotation>
@@ -6017,7 +5480,7 @@ References to a logger to use as logger for the error handler.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Logging level to use by error handler. Default value: ERROR
+The logging level to use when logging caught exceptions. Default value: ERROR
]]>
</xs:documentation>
</xs:annotation>
@@ -6035,8 +5498,8 @@ Name of the logger to use by the error handler.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a processor that should be processed before a redelivery attempt. Can be used to change the
-org.apache.camel.Exchange before its being redelivered.
+Sets a reference to a processor that is invoked before each redelivery attempt. Can be used to change the exchange
+before it is redelivered.
]]>
</xs:documentation>
</xs:annotation>
@@ -6045,9 +5508,8 @@ org.apache.camel.Exchange before its being redelivered.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a processor that should be processed just after an exception occurred. Can be used to perform custom
-logging about the occurred exception at the exact time it happened. Important: Any exception thrown from this processor
-will be ignored.
+Sets a reference to a processor that is invoked just after an exception occurred. Can be used to perform custom logging.
+Any exception thrown from this processor is ignored.
]]>
</xs:documentation>
</xs:annotation>
@@ -6056,8 +5518,8 @@ will be ignored.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a processor to prepare the org.apache.camel.Exchange before handled by the failure processor / dead
-letter channel. This allows for example to enrich the message before sending to a dead letter queue.
+Sets a reference to a processor to prepare the exchange before handled by the failure processor or dead letter channel.
+This allows for example to enrich the message before sending to a dead letter queue.
]]>
</xs:documentation>
</xs:annotation>
@@ -6066,7 +5528,7 @@ letter channel. This allows for example to enrich the message before sending to
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a retry while predicate. Will continue retrying until the predicate evaluates to false.
+Sets a reference to a retry while predicate. Redelivery continues as long as the predicate evaluates to true.
]]>
</xs:documentation>
</xs:annotation>
@@ -6075,7 +5537,7 @@ Sets a retry while predicate. Will continue retrying until the predicate evaluat
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a thread pool to be used by the error handler.
+Sets a reference to a thread pool to be used for asynchronous redelivery.
]]>
</xs:documentation>
</xs:annotation>
@@ -6098,7 +5560,7 @@ Sets a reference to a thread pool to be used by the error handler.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum redeliveries x = redeliver at most x times 0 = no redeliveries -1 = redeliver forever.
+Sets the maximum number of redeliveries. Use 0 for no redeliveries, or -1 to redeliver forever.
]]>
</xs:documentation>
</xs:annotation>
@@ -6107,7 +5569,7 @@ Sets the maximum redeliveries x = redeliver at most x times 0 = no redeliveries
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the initial redelivery delay. Default value: 1000
+Sets the initial delay in milliseconds before the first redelivery attempt. Default value: 1000
]]>
</xs:documentation>
</xs:annotation>
@@ -6126,7 +5588,8 @@ Routing Engine (e.g. seda). Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the back off multiplier. Default value: 2.0
+Sets the multiplier applied to the previous redelivery delay to compute the next delay when using exponential backoff.
+Default value: 2.0
]]>
</xs:documentation>
</xs:annotation>
@@ -6135,7 +5598,8 @@ Sets the back off multiplier. Default value: 2.0
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Turn on exponential back off. Default value: false
+Enables exponential backoff, so each subsequent redelivery delay is multiplied by the backOffMultiplier. Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -6144,7 +5608,8 @@ Turn on exponential back off. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the collision avoidance factor. Default value: 0.15
+Sets the collision avoidance factor, which adds a random percentage of the delay to avoid thundering herd problems when
+multiple redeliveries happen simultaneously. Default value: 0.15
]]>
</xs:documentation>
</xs:annotation>
@@ -6153,7 +5618,8 @@ Sets the collision avoidance factor. Default value: 0.15
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Turn on collision avoidance. Default value: false
+Enables collision avoidance, which adds a random factor to redelivery delays to prevent multiple simultaneous
+redeliveries from colliding. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -6162,7 +5628,8 @@ Turn on collision avoidance. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum delay between redelivery. Default value: 60000
+Sets the upper bound on redelivery delay in milliseconds when using exponential backoff, to prevent delays from growing
+unbounded. Default value: 60000
]]>
</xs:documentation>
</xs:annotation>
@@ -6171,7 +5638,8 @@ Sets the maximum delay between redelivery. Default value: 60000
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the logging level to use when retries have been exhausted. Default value: ERROR
+Sets the logging level to use when all retries have been exhausted and the message is moved to the dead letter channel
+or failed. Default value: ERROR
]]>
</xs:documentation>
</xs:annotation>
@@ -6180,7 +5648,7 @@ Sets the logging level to use when retries have been exhausted. Default value: E
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the logging level to use for logging retry attempts. Default value: DEBUG
+Sets the logging level to use when a redelivery attempt is made. Default value: DEBUG
]]>
</xs:documentation>
</xs:annotation>
@@ -6189,7 +5657,7 @@ Sets the logging level to use for logging retry attempts. Default value: DEBUG
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the interval to use for logging retry attempts. Default value: 1
+Sets how often to log redelivery attempts. For example, a value of 3 logs every 3rd redelivery attempt. Default value: 1
]]>
</xs:documentation>
</xs:annotation>
@@ -6198,7 +5666,7 @@ Sets the interval to use for logging retry attempts. Default value: 1
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether retry attempts should be logged or not. Can be used to include or reduce verbose. Default value: true
+Whether retry attempts should be logged or not. Can be used to include or reduce verbose logging. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -6207,7 +5675,7 @@ Sets whether retry attempts should be logged or not. Can be used to include or r
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether stack traces should be logged. Can be used to include or reduce verbose. Default value: true
+Whether stack traces should be logged. Can be used to include or reduce verbose logging. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -6216,7 +5684,7 @@ Sets whether stack traces should be logged. Can be used to include or reduce ver
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether stack traces should be logged when an retry attempt failed. Can be used to include or reduce verbose.
+Whether stack traces should be logged when a retry attempt failed. Can be used to include or reduce verbose logging.
Default value: false
]]>
</xs:documentation>
@@ -6226,7 +5694,8 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether handled exceptions should be logged or not. Can be used to include or reduce verbose. Default value: false
+Whether handled exceptions should be logged or not. Can be used to include or reduce verbose logging. Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -6235,8 +5704,8 @@ Sets whether handled exceptions should be logged or not. Can be used to include
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether new exceptions should be logged or not. Can be used to include or reduce verbose. A new exception is an
-exception that was thrown while handling a previous exception. Default value: true
+Whether new exceptions should be logged or not. A new exception is an exception that was thrown while handling a
+previous exception. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -6245,7 +5714,7 @@ exception that was thrown while handling a previous exception. Default value: tr
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether continued exceptions should be logged or not. Can be used to include or reduce verbose. Default value:
+Whether continued exceptions should be logged or not. Can be used to include or reduce verbose logging. Default value:
false
]]>
</xs:documentation>
@@ -6255,7 +5724,8 @@ false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether exhausted exceptions should be logged or not. Can be used to include or reduce verbose. Default value: true
+Whether exhausted exceptions should be logged or not. Can be used to include or reduce verbose logging. Default value:
+true
]]>
</xs:documentation>
</xs:annotation>
@@ -6264,8 +5734,8 @@ Sets whether exhausted exceptions should be logged or not. Can be used to includ
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether exhausted exceptions should be logged including message history or not (supports property placeholders).
-Can be used to include or reduce verbose. Default value: false
+Whether exhausted exceptions should be logged including message history. Can be used to include or reduce verbose
+logging. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -6274,8 +5744,8 @@ Can be used to include or reduce verbose. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether exhausted message body should be logged including message history or not (supports property placeholders).
-Can be used to include or reduce verbose. Requires logExhaustedMessageHistory to be enabled. Default value: false
+Whether exhausted message body should be logged including message history. Requires logExhaustedMessageHistory to be
+enabled. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -6293,7 +5763,8 @@ Disables redelivery (same as setting maximum redeliveries to 0). Default value:
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the delay pattern with delay intervals.
+Sets the delay pattern for redeliveries using a pattern such as '0:1000;5:5000;10:30000' where each entry maps a
+redelivery count to a delay in milliseconds (e.g. redeliveries 0-4 use 1s delay, 5-9 use 5s, 10 use 30s).
]]>
</xs:documentation>
</xs:annotation>
@@ -6334,7 +5805,7 @@ Sets the reference of the instance of org.apache.camel.spi.ExchangeFormatter to
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-References to an existing or custom error handler.
+Reference to an existing or custom error handler to lookup from the registry.
]]>
</xs:documentation>
</xs:annotation>
@@ -6367,7 +5838,7 @@ configured then Camel will attempt to auto-discover.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the logging level to use for logging transactional rollback. This option is default WARN. Default value: WARN
+The logging level to use for logging transactional rollback. Default is WARN. Default value: WARN
]]>
</xs:documentation>
</xs:annotation>
@@ -6395,6 +5866,7 @@ Sets the logging level to use for logging transactional rollback. This option is
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -6416,6 +5888,7 @@ Sets the logging level to use for logging transactional rollback. This option is
<xs:element ref="tns:xquery"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -6486,15 +5959,13 @@ Sets the logging level to use for logging transactional rollback. This option is
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="statusPropertyName" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of exchange property to use for storing the status of the filtering. Setting this allows to know if the filter
-predicate evaluated as true or false.
+Name of an exchange property to store whether the filter predicate matched or not. The value is stored as a boolean.
]]>
</xs:documentation>
</xs:annotation>
@@ -6507,6 +5978,7 @@ predicate evaluated as true or false.
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -6577,7 +6049,6 @@ predicate evaluated as true or false.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -6591,7 +6062,7 @@ predicate evaluated as true or false.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the URI of the endpoint to use.
+The endpoint URI to consume from.
]]>
</xs:documentation>
</xs:annotation>
@@ -6600,8 +6071,8 @@ Sets the URI of the endpoint to use.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a variable to store a copy of the received message body (only body, not headers). This is handy for easy access
-to the received message body via variables.
+To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -6648,6 +6119,7 @@ Global option value.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -6669,6 +6141,7 @@ Global option value.
<xs:element ref="tns:xquery"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -6739,14 +6212,13 @@ Global option value.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="idempotentRepository" type="xs:string" use="required">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the reference name of the message id repository.
+Sets the reference name of the message id repository to use for storing processed message ids to detect duplicates.
]]>
</xs:documentation>
</xs:annotation>
@@ -6765,13 +6237,7 @@ default enabled. Default value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether to complete the idempotent consumer eager or when the exchange is done. If this option is true to complete
-eager, then the idempotent consumer will trigger its completion when the exchange reached the end of the block of the
-idempotent consumer pattern. So if the exchange is continued routed after the block ends, then whatever happens there
-does not affect the state. If this option is false (default) to not complete eager, then the idempotent consumer will
-complete when the exchange is done being routed. So if the exchange is continued routed after the block ends, then
-whatever happens there also affect the state. For example if the exchange failed due to an exception, then the state of
-the idempotent consumer will be a rollback. Default value: false
+Sets whether to complete the idempotent consumer eager or when the exchange is done. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -6780,9 +6246,7 @@ the idempotent consumer will be a rollback. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether to skip duplicates or not. The default behavior is to skip duplicates. A duplicate message would have the
-Exchange property org.apache.camel.Exchange#DUPLICATE_MESSAGE set to a Boolean#TRUE value. A none duplicate message will
-not have this property set. Default value: true
+Sets whether to skip duplicates or not. The default behavior is to skip duplicates. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -6808,7 +6272,8 @@ true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The input type URN.
+The input type URN in the format 'scheme:name' (e.g. 'java:com.example.MyClass' or 'json:JsonOrder'). Declares the
+expected data type for messages consumed by this route.
]]>
</xs:documentation>
</xs:annotation>
@@ -6817,7 +6282,7 @@ The input type URN.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether if validation is required for this input type. Default value: false
+Whether validation is required for this input type. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -6831,6 +6296,7 @@ Whether if validation is required for this input type. Default value: false
<xs:sequence>
<xs:element minOccurs="0" ref="tns:onWhen"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -6901,7 +6367,6 @@ Whether if validation is required for this input type. Default value: false
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -6915,8 +6380,7 @@ Whether if validation is required for this input type. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Intercept incoming messages from the uri or uri pattern. If this option is not configured, then all incoming messages is
-intercepted.
+Intercept incoming messages from the uri or uri pattern. If not configured, then all incoming messages are intercepted.
]]>
</xs:documentation>
</xs:annotation>
@@ -6930,6 +6394,7 @@ intercepted.
<xs:sequence>
<xs:element minOccurs="0" ref="tns:onWhen"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -7000,7 +6465,6 @@ intercepted.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="uri" type="xs:string" use="required">
@@ -7016,8 +6480,8 @@ Intercept sending to the uri or uri pattern.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If set to true then the message is not sent to the original endpoint. By default (false) the message is both intercepted
-and then sent to the original endpoint.
+Whether to skip sending the message to the original endpoint. By default, the message is both intercepted and then sent
+to the original endpoint. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7039,6 +6503,7 @@ After sending to the endpoint then send the message to this uri which allows to
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -7109,7 +6574,6 @@ After sending to the endpoint then send the message to this uri which allows to
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="name" type="xs:string" use="required">
@@ -7139,6 +6603,7 @@ mynamecount=4&type=gold.
<xs:element ref="tns:weightedLoadBalancer"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -7209,7 +6674,6 @@ mynamecount=4&type=gold.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -7257,11 +6721,8 @@ monitored.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the failover load balancer should operate in round robin mode or not. If not, then it will always start
-from the first endpoint when a new message is to be processed. In other words it restart from the top for every message.
-If round robin is enabled, then it keeps state and will continue with the next endpoint in a round robin fashion. You
-can also enable sticky mode together with round robin, if so then it will pick the last known good endpoint to use when
-starting the load balancing (instead of using the next when starting).
+Whether to use round robin mode. If enabled, the load balancer keeps state and continues with the next endpoint in a
+round robin fashion. If not, it always starts from the first endpoint for every message. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7270,11 +6731,8 @@ starting the load balancing (instead of using the next when starting).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the failover load balancer should operate in sticky mode or not. If not, then it will always start from
-the first endpoint when a new message is to be processed. In other words it restart from the top for every message. If
-sticky is enabled, then it keeps state and will continue with the last known good endpoint. You can also enable sticky
-mode together with round robin, if so then it will pick the last known good endpoint to use when starting the load
-balancing (instead of using the next when starting).
+Whether to use sticky mode. If enabled, the load balancer keeps state and continues with the last known good endpoint.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7284,8 +6742,8 @@ balancing (instead of using the next when starting).
<xs:documentation xml:lang="en">
<![CDATA[
A value to indicate after X failover attempts we should exhaust (give up). Use -1 to indicate never give up and
-continuously try to failover. Use 0 to never failover. And use e.g. 3 to failover at most 3 times before giving up. This
-option can be used whether roundRobin is enabled or not. Default value: -1
+continuously try to failover. Use 0 to never failover. Use e.g. 3 to failover at most 3 times before giving up. Default
+value: -1
]]>
</xs:documentation>
</xs:annotation>
@@ -7294,10 +6752,8 @@ option can be used whether roundRobin is enabled or not. Default value: -1
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To turn off Camel error handling during load balancing. By default, Camel error handler will attempt calling a service,
-which means you can specify retires and other fine-grained settings. And only when Camel error handler have failed all
-attempts, then this load balancer will fail over to the next endpoint and try again. You can turn this off, and then
-this load balancer will fail over immediately on an error. Default value: true
+Whether to inherit the error handler. If turned off, the load balancer will fail over immediately on an error instead of
+waiting for Camel error handler to exhaust retries. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -7351,7 +6807,7 @@ The correlation expression to use to calculate the correlation key.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The distribution ratio is a delimited String consisting on integer weights separated by delimiters for example 2,3,5.
+The distribution ratio is a delimited String consisting of integer weights separated by delimiters for example 2,3,5.
The distributionRatio must match the number of endpoints and/or processors specified in the load balancer list.
]]>
</xs:documentation>
@@ -7361,7 +6817,7 @@ The distributionRatio must match the number of endpoints and/or processors speci
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Delimiter used to specify the distribution ratio. The default value is , (comma). Default value: ,
+Delimiter used to specify the distribution ratio. The default value is comma. Default value: ,
]]>
</xs:documentation>
</xs:annotation>
@@ -7370,8 +6826,7 @@ Delimiter used to specify the distribution ratio. The default value is , (comma)
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To enable round robin mode. By default the weighted distribution mode is used. The default value is false. Default
-value: false
+Whether to enable round robin mode. By default the weighted distribution mode is used. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7387,7 +6842,7 @@ value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the log message (uses simple language).
+The log message to output. Supports simple language expressions.
]]>
</xs:documentation>
</xs:annotation>
@@ -7396,7 +6851,8 @@ Sets the log message (uses simple language).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the logging level. The default value is INFO. Default value: INFO
+Sets the logging level to use for the log message. Available levels: TRACE, DEBUG, INFO, WARN, ERROR, OFF. Default
+value: INFO
]]>
</xs:documentation>
</xs:annotation>
@@ -7405,12 +6861,7 @@ Sets the logging level. The default value is INFO. Default value: INFO
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the name of the logger. The name is default the routeId or the source:line if source location is enabled. You can
-also specify the name using tokens: ${class} - the logger class name (org.apache.camel.processor.LogProcessor)
-${contextId} - the camel context id ${routeId} - the route id ${groupId} - the route group id ${nodeId} - the node id
-${nodePrefixId} - the node prefix id ${source} - the source:line (source location must be enabled) ${source.name} - the
-source filename (source location must be enabled) ${source.line} - the source line number (source location must be
-enabled) For example to use the route and node id you can specify the name as: ${routeId}/${nodeId}.
+The logger name to use. By default the route id is used.
]]>
</xs:documentation>
</xs:annotation>
@@ -7419,7 +6870,7 @@ enabled) For example to use the route and node id you can specify the name as: $
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use slf4j marker.
+An optional SLF4J marker to use with the log statement.
]]>
</xs:documentation>
</xs:annotation>
@@ -7428,7 +6879,7 @@ To use slf4j marker.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To refer to a custom logger instance to lookup from the registry.
+Reference to a custom SLF4J logger instance to use.
]]>
</xs:documentation>
</xs:annotation>
@@ -7437,8 +6888,7 @@ To refer to a custom logger instance to lookup from the registry.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To configure the language to use. By default, the simple language is used. However, Camel also supports other languages
-such as groovy.
+The language to use for evaluating the log message, such as simple, groovy, or ognl.
]]>
</xs:documentation>
</xs:annotation>
@@ -7459,6 +6909,7 @@ such as groovy.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -7480,6 +6931,7 @@ such as groovy.
<xs:element ref="tns:xquery"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -7550,16 +7002,14 @@ such as groovy.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="copy" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If the copy attribute is true, a copy of the input Exchange is used for each iteration. That means each iteration will
-start from a copy of the same message. By default loop will loop the same exchange all over, so each iteration may have
-different message content. Default value: false
+If enabled, a copy of the input Exchange is used for each iteration. That means each iteration will start from a copy of
+the same message. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7577,8 +7027,7 @@ Enables the while loop that loops until the predicate evaluates to false or null
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If the breakOnShutdown attribute is true, then the loop will not iterate until it reaches the end when Camel is shut
-down. Default value: false
+If enabled, the loop will not iterate until it reaches the end when Camel is shut down. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7587,8 +7036,8 @@ down. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Uses the Processor when preparing the org.apache.camel.Exchange for each loop iteration. This can be used to deep-clone
-messages, or any custom logic needed before the looping executes.
+Uses a processor when preparing the exchange for each loop iteration. This can be used to deep-clone messages, or any
+custom logic needed before the looping executes.
]]>
</xs:documentation>
</xs:annotation>
@@ -7617,6 +7066,7 @@ messages, or any custom logic needed before the looping executes.
<xs:element ref="tns:flatpack"/>
<xs:element ref="tns:fory"/>
<xs:element ref="tns:grok"/>
+ <xs:element ref="tns:groovyJson"/>
<xs:element ref="tns:groovyXml"/>
<xs:element ref="tns:gzipDeflater"/>
<xs:element ref="tns:hl7"/>
@@ -7630,6 +7080,8 @@ messages, or any custom logic needed before the looping executes.
<xs:element ref="tns:mimeMultipart"/>
<xs:element ref="tns:ocsf"/>
<xs:element ref="tns:parquetAvro"/>
+ <xs:element ref="tns:pgp"/>
+ <xs:element ref="tns:pqc"/>
<xs:element ref="tns:protobuf"/>
<xs:element ref="tns:rss"/>
<xs:element ref="tns:smooks"/>
@@ -7643,8 +7095,6 @@ messages, or any custom logic needed before the looping executes.
<xs:element ref="tns:univocityFixed"/>
<xs:element ref="tns:univocityTsv"/>
<xs:element ref="tns:xmlSecurity"/>
- <xs:element ref="tns:pgp"/>
- <xs:element ref="tns:pqc"/>
<xs:element ref="tns:yaml"/>
<xs:element ref="tns:zipDeflater"/>
<xs:element ref="tns:zipFile"/>
@@ -7655,9 +7105,7 @@ messages, or any custom logic needed before the looping executes.
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to
-easily control what data to use for sending and receiving. Important: When using send variable then the message body is
-taken from this variable instead of the current message, however the headers from the message will still be used as
-well. In other words, the variable is used instead of the message body, but everything else is as usual.
+easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -7667,8 +7115,7 @@ well. In other words, the variable is used instead of the message body, but ever
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
-user data and to easily control what data to use for sending and receiving. Important: When using receive variable then
-the received body is stored only in this variable and not on the current message.
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -7693,8 +7140,8 @@ Class to use when unmarshalling.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If the asn1 file has more than one entry, the setting this option to true, allows working with the splitter EIP, to
-split the data using an iterator in a streaming mode. Default value: false
+If the asn1 file has more than one entry, the setting this option to true allows working with the splitter EIP to split
+each entry individually. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7785,8 +7232,7 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to
-use different collection types than java.util.Collection based as default.
+Refers to a custom collection type to lookup in the registry to use.
]]>
</xs:documentation>
</xs:annotation>
@@ -7823,10 +7269,8 @@ To use custom Jackson modules referred from the Camel registry. Multiple modules
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that
-matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. Multiple features can be separated
+by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -7835,10 +7279,8 @@ can be separated by comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name
-that matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. Multiple features can be
+separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -7847,8 +7289,8 @@ can be separated by comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If enabled then Jackson is allowed to attempt to use the CamelJacksonUnmarshalType header during the unmarshalling. This
-should only be enabled when desired to be used. Default value: false
+If enabled then Jackson is allowed to attempt to use the CamelJacksonUnmarshalType header during the unmarshalling.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -7963,7 +7405,7 @@ To specific a maximum line length for the encoded data. By default 76 is used. D
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The line separators to use. Uses new line characters (CRLF) by default.
+The line separators to use. By default \r\n is used.
]]>
</xs:documentation>
</xs:annotation>
@@ -7972,8 +7414,8 @@ The line separators to use. Uses new line characters (CRLF) by default.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Instead of emitting '' and '/' we emit '-' and '_' respectively. urlSafe is only applied to encode operations. Decoding
-seamlessly handles both modes. Is by default false. Default value: false
+Instead of emitting and / we emit - and _ respectively. urlSafe is only applied to encode operations. Decoding
+seamlessly handles both modes. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8045,8 +7487,7 @@ The charset to use. Is by default the JVM platform default charset.
<xs:documentation xml:lang="en">
<![CDATA[
To use a custom org.apache.camel.dataformat.beanio.BeanIOErrorHandler as error handler while parsing. Configure the
-fully qualified class name of the error handler. Notice the options ignoreUnidentifiedRecords, ignoreUnexpectedRecords,
-and ignoreInvalidRecords may not be in use when you use a custom error handler.
+fully qualified class name of the error handler.
]]>
</xs:documentation>
</xs:annotation>
@@ -8055,9 +7496,7 @@ and ignoreInvalidRecords may not be in use when you use a custom error handler.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-This options controls whether to unmarshal as a list of objects or as a single object only. The former is the default
-mode, and the latter is only intended in special use-cases where beanio maps the Camel message to a single POJO bean.
-Default value: false
+This option controls whether to unmarshal as a list of objects or as a single object only. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8164,8 +7603,7 @@ Class name of the java type to use when unmarshalling.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to
-use different collection types than java.util.Collection based as default.
+Refers to a custom collection type to lookup in the registry to use.
]]>
</xs:documentation>
</xs:annotation>
@@ -8184,7 +7622,7 @@ To unmarshal to a List of Map or a List of Pojo. Default value: false
<xs:documentation xml:lang="en">
<![CDATA[
If enabled then Jackson CBOR is allowed to attempt to use the CamelCBORUnmarshalType header during the unmarshalling.
-This should only be enabled when desired to be used. Default value: false
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8212,10 +7650,7 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that
-matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to enable on the Jackson ObjectMapper. Multiple features can be separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -8224,10 +7659,7 @@ can be separated by comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name
-that matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to disable on the Jackson ObjectMapper. Multiple features can be separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -8279,8 +7711,7 @@ Refers to a byte array containing the Initialization Vector that will be used to
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A JCE AlgorithmParameterSpec used to initialize the Cipher. Will lookup the type using the given name as a
-java.security.spec.AlgorithmParameterSpec type.
+A JCE AlgorithmParameterSpec used to initialize the Cipher.
]]>
</xs:documentation>
</xs:annotation>
@@ -8361,7 +7792,7 @@ Sets the comment marker of the reference format.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the delimiter to use. The default value is , (comma).
+The delimiter to use. The default value is , (comma).
]]>
</xs:documentation>
</xs:annotation>
@@ -8370,7 +7801,7 @@ Sets the delimiter to use. The default value is , (comma).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Use for disabling using escape character. Default value: false
+Whether to disable the escape character. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8388,7 +7819,7 @@ Sets the escape character to use.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Use for disabling headers. Default value: false
+Whether to disable headers. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8433,7 +7864,7 @@ Whether to ignore surrounding spaces. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Used to disable null strings. Default value: false
+Whether to disable null string handling. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8451,7 +7882,7 @@ Sets the null string.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Used to disable quotes. Default value: false
+Whether to disable quoting. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8460,7 +7891,7 @@ Used to disable quotes. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the quote to use which by default is double-quote character.
+The quote character to use. The default is double-quote character.
]]>
</xs:documentation>
</xs:annotation>
@@ -8469,7 +7900,7 @@ Sets the quote to use which by default is double-quote character.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Used for disabling record separator.
+Whether to disable the record separator. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8478,7 +7909,7 @@ Used for disabling record separator.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the record separator (aka new line) which by default is new line characters (CRLF).
+The record separator (aka new line) which by default is new line characters (CRLF).
]]>
</xs:documentation>
</xs:annotation>
@@ -8505,7 +7936,7 @@ Sets the quote mode.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether or not to ignore case when accessing header names. Default value: false
+Whether to ignore case when accessing header names. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8514,7 +7945,7 @@ Sets whether or not to ignore case when accessing header names. Default value: f
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether or not to trim leading and trailing blanks. Default value: false
+Whether to trim leading and trailing blanks. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8523,7 +7954,7 @@ Sets whether or not to trim leading and trailing blanks. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether or not to add a trailing delimiter. Default value: false
+Whether to add a trailing delimiter. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8533,7 +7964,7 @@ Sets whether or not to add a trailing delimiter. Default value: false
<xs:documentation xml:lang="en">
<![CDATA[
Sets the implementation of the CsvMarshallerFactory interface which is able to customize marshalling/unmarshalling
-behavior by extending CsvMarshaller or creating it from scratch.
+behavior.
]]>
</xs:documentation>
</xs:annotation>
@@ -8552,8 +7983,8 @@ one. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether the unmarshalling should produce maps (HashMap)for the lines values instead of lists. It requires to have header
-(either defined or collected). Default value: false
+Whether the unmarshalling should produce maps (HashMap) for the lines values instead of lists. It requires to have
+header (either defined or collected). Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8597,7 +8028,7 @@ Whether the unmarshalling should capture the header record and store it in the m
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to the custom org.apache.camel.spi.DataFormat to lookup from the Camel registry.
+Reference to the custom DataFormat to lookup from the Camel registry.
]]>
</xs:documentation>
</xs:annotation>
@@ -8654,7 +8085,7 @@ The root namespace of the schema to use.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The version of FHIR to use. Possible values are: DSTU2,DSTU2_HL7ORG,DSTU2_1,DSTU3,R4,R5. Default value: R4
+The version of FHIR to use. Possible values are: DSTU2, DSTU2_HL7ORG, DSTU2_1, DSTU3, R4, R5. Default value: R4
]]>
</xs:documentation>
</xs:annotation>
@@ -8673,7 +8104,7 @@ To use a custom fhir context. Reference to object of type ca.uhn.fhir.context.Fh
<xs:documentation xml:lang="en">
<![CDATA[
Sets the pretty print flag, meaning that the parser will encode resources with human-readable spacing and newlines
-between elements instead of condensing output as much as possible. Default value: false
+between elements. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8702,10 +8133,8 @@ object of type ca.uhn.fhir.context.ParserOptions.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If set (FQN class names), when parsing resources the parser will try to use the given types when possible, in the order
-that they are provided (from highest to lowest priority). For example, if a custom type which declares to implement the
-Patient resource is passed in here, and the parser is parsing a Bundle containing a Patient resource, the parser will
-use the given custom type. Multiple class names can be separated by comma.
+If set (FQN class names), when parsing resources the parser will try to use the given types when possible. Multiple
+class names can be separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -8734,9 +8163,8 @@ references if they are provided as absolute URLs but have a base matching the gi
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If set to true (default is false) the ID of any resources being encoded will not be included in the output. Note that
-this does not apply to contained resources, only to root resources. In other words, if this is set to true, contained
-resources will still have local IDs but the outer/containing ID will not have an ID. Default value: false
+If set to true (default is false) the ID of any resources being encoded will not be included in the output. Default
+value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8745,9 +8173,8 @@ resources will still have local IDs but the outer/containing ID will not have an
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If set to true (default is false), the values supplied to setEncodeElements(Set) will not be applied to the root
-resource (typically a Bundle), but will be applied to any sub-resources contained within it (i.e. search result
-resources in that bundle). Default value: false
+If set to true (default is false), the values supplied to setEncodeElements will not be applied to the root resource
+(typically a Bundle), but will be applied to any sub-resources contained within it. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8757,10 +8184,7 @@ resources in that bundle). Default value: false
<xs:documentation xml:lang="en">
<![CDATA[
If provided, specifies the elements which should be encoded, to the exclusion of all others. Multiple elements can be
-separated by comma when using String parameter. Valid values for this field would include: Patient - Encode patient and
-all its children Patient.name - Encode only the patient's name Patient.name.family - Encode only the patient's family
-name .text - Encode the text element on any resource (only the very first position may contain a wildcard) .(mandatory)
-- This is a special case which causes any mandatory fields (min 0) to be encoded.
+separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -8769,12 +8193,7 @@ name .text - Encode the text element on any resource (only the very first positi
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If provided, specifies the elements which should NOT be encoded. Multiple elements can be separated by comma when using
-String parameter. Valid values for this field would include: Patient - Don't encode patient and all its children
-Patient.name - Don't encode the patient's name Patient.name.family - Don't encode the patient's family name .text -
-Don't encode the text element on any resource (only the very first position may contain a wildcard) DSTU2 note: Note
-that values including meta, such as Patient.meta will work for DSTU2 parsers, but values with subelements on meta such
-as Patient.meta.lastUpdated will only work in DSTU3 mode.
+If provided, specifies the elements which should NOT be encoded. Multiple elements can be separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -8784,11 +8203,7 @@ as Patient.meta.lastUpdated will only work in DSTU3 mode.
<xs:documentation xml:lang="en">
<![CDATA[
If set to true (which is the default), resource references containing a version will have the version removed when the
-resource is encoded. This is generally good behaviour because in most situations, references from one resource to
-another should be to the resource by ID, not by ID and version. In some cases though, it may be desirable to preserve
-the version in resource links. In that case, this value should be set to false. This method provides the ability to
-globally disable reference encoding. If finer-grained control is needed, use
-setDontStripVersionsFromReferencesAtPaths(List). Default value: false
+resource is encoded. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8798,9 +8213,7 @@ setDontStripVersionsFromReferencesAtPaths(List). Default value: false
<xs:documentation xml:lang="en">
<![CDATA[
If set to true (which is the default), the Bundle.entry.fullUrl will override the Bundle.entry.resource's resource id if
-the fullUrl is defined. This behavior happens when parsing the source data into a Bundle object. Set this to false if
-this is not the desired behavior (e.g. the client code wishes to perform additional validation checks between the
-fullUrl and the resource id). Default value: false
+the fullUrl is defined. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -8829,10 +8242,7 @@ If set to true (default is false), narratives will not be included in the encode
<xs:documentation xml:lang="en">
<![CDATA[
If supplied value(s), any resource references at the specified paths will have their resource versions encoded instead
-of being automatically stripped during the encoding process. This setting has no effect on the parsing process. Multiple
-elements can be separated by comma when using String parameter. This method provides a finer-grained level of control
-than setStripVersionsFromReferences(String) and any paths specified by this method will be encoded even if
-setStripVersionsFromReferences(String) has been set to true (which is the default).
+of being automatically stripped during the encoding process. Multiple elements can be separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -8997,8 +8407,8 @@ The grok pattern to match lines of input.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Turns on flattened mode. In flattened mode the exception is thrown when there are multiple pattern matches with same
-key. Default value: false
+Whether to use flattened mode. In flattened mode an exception is thrown when there are multiple pattern matches with the
+same key. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9007,8 +8417,8 @@ key. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If false, every line of input is matched for pattern only once. Otherwise the line can be scanned multiple times when
-non-terminal pattern is used. Default value: true
+Whether to allow multiple matches per line. If false, every line of input is matched for the pattern only once.
+Otherwise the line can be scanned multiple times when a non-terminal pattern is used. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -9018,6 +8428,22 @@ non-terminal pattern is used. Default value: true
<xs:documentation xml:lang="en">
<![CDATA[
Whether to capture named expressions only or not (i.e. %{IP:ip} but not ${IP}). Default value: false
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="groovyJSonDataFormat">
+ <xs:complexContent>
+ <xs:extension base="tns:dataFormat">
+ <xs:sequence/>
+ <xs:attribute name="prettyPrint" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Whether to pretty print output nicely formatted. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -9033,8 +8459,8 @@ Whether to capture named expressions only or not (i.e. %{IP:ip} but not ${IP}).
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To turn on or off attribute mapping. When enabled then keys that start with _ or character will be mapped to an XML
-attribute, and vise versa. This rule is what Jackson and other XML or JSon libraries uses. Default value: true
+Whether to enable attribute mapping. When enabled, keys that start with _ or character will be mapped to an XML
+attribute, and vice versa. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -9066,7 +8492,17 @@ To use a custom HL7 parser.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to validate the HL7 message Is by default true. Default value: true
+Whether to validate the HL7 message. Default value: true
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="targetFormat" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The target format for marshal output and unmarshal result type. By default, marshal encodes to HL7 ER7 and unmarshal
+returns a HAPI Message object. If set to XML, marshal encodes to HL7 XML and unmarshal returns an XML DOM Document.
]]>
</xs:documentation>
</xs:annotation>
@@ -9082,7 +8518,7 @@ Whether to validate the HL7 message Is by default true. Default value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to validate. Default value: false
+Whether to validate the iCal document. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9141,7 +8577,7 @@ Lookup and use the existing XmlMapper with the given id.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To enable pretty printing output nicely formatted. Is by default false. Default value: false
+Whether to enable pretty printing output nicely formatted. Is by default false. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9159,8 +8595,8 @@ Class name of the java type to use when unmarshalling.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If enabled then Jackson is allowed to attempt to use the CamelJacksonUnmarshalType header during the unmarshalling. This
-should only be enabled when desired to be used. Default value: false
+Whether to allow Jackson to use the CamelJacksonUnmarshalType header during unmarshalling. Should only be enabled when
+desired. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9179,7 +8615,7 @@ JSON views to accomplish this. This option is to refer to the class which has Js
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If you want to marshal a pojo to JSON, and the pojo has some fields with null values. And you want to skip these null
+If you want to marshal a POJO to JSON, and the POJO has some fields with null values. And you want to skip these null
values, you can set this option to NON_NULL.
]]>
</xs:documentation>
@@ -9189,8 +8625,8 @@ values, you can set this option to NON_NULL.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Used for JMS users to allow the JMSType header from the JMS spec to specify a FQN classname to use to unmarshal to.
-Default value: false
+Whether to allow the JMSType header from the JMS spec to specify a FQN classname to use to unmarshal to. Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -9199,8 +8635,8 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to
-use different collection types than java.util.Collection based as default.
+Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows using
+different collection types than java.util.Collection based as default.
]]>
</xs:documentation>
</xs:annotation>
@@ -9209,7 +8645,7 @@ use different collection types than java.util.Collection based as default.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To unmarshal to a List of Map or a List of Pojo. Default value: false
+Whether to unmarshal to a List of Map or a List of Pojo. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9227,7 +8663,7 @@ If set then Jackson will use the Timezone when marshalling/unmarshalling.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to enable the JAXB annotations module when using jackson. When enabled then JAXB annotations can be used by
+Whether to enable the JAXB annotations module when using Jackson. When enabled then JAXB annotations can be used by
Jackson. Default value: false
]]>
</xs:documentation>
@@ -9257,9 +8693,8 @@ To use custom Jackson modules referred from the Camel registry. Multiple modules
<xs:documentation xml:lang="en">
<![CDATA[
Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that
-matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+matches a enum from SerializationFeature, DeserializationFeature, or MapperFeature. Multiple features can be separated
+by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -9269,9 +8704,8 @@ can be separated by comma.
<xs:documentation xml:lang="en">
<![CDATA[
Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name
-that matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+that matches a enum from SerializationFeature, DeserializationFeature, or MapperFeature. Multiple features can be
+separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -9291,10 +8725,8 @@ value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum string length (in chars or bytes, depending on input context). The default is 20,000,000. This limit is
-not exact, the limit is applied when we increase internal buffer sizes and an exception will happen at sizes greater
-than this limit. Some text values that are a little bigger than the limit may be treated as valid but no text values
-with sizes less than or equal to this limit will be treated as invalid.
+Maximum allowed string length when deserializing (in chars or bytes, depending on input context). The default is
+20,000,000.
]]>
</xs:documentation>
</xs:annotation>
@@ -9329,8 +8761,8 @@ false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To validate against an existing schema. Your can use the prefix classpath:, file: or http: to specify how the resource
-should be resolved. You can separate multiple schema files by using the ',' character.
+To validate against an existing schema. You can use the prefix classpath:, file: or http: to specify how the resource
+should be resolved. You can separate multiple schema files by using the comma character.
]]>
</xs:documentation>
</xs:annotation>
@@ -9339,10 +8771,9 @@ should be resolved. You can separate multiple schema files by using the ',' char
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the schema severity level to use when validating against a schema. This level determines the minimum severity error
-that triggers JAXB to stop continue parsing. The default value of 0 (warning) means that any error (warning, error or
-fatal error) will trigger JAXB to stop. There are the following three levels: 0=warning, 1=error, 2=fatal error. Default
-value: 0
+Sets the schema severity level to use when validating against a schema. The default value of 0 (warning) means that any
+error will trigger JAXB to stop. There are the following three levels: 0=warning, 1=error, 2=fatal error. Default value:
+0
]]>
</xs:documentation>
</xs:annotation>
@@ -9360,8 +8791,7 @@ To enable pretty printing output nicely formatted. Is by default false. Default
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to allow using ObjectFactory classes to create the POJO classes during marshalling. This only applies to POJO
-classes that has not been annotated with JAXB and providing jaxb.index descriptor files. Default value: true
+Whether to allow using ObjectFactory classes to create the POJO classes during marshalling. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -9379,7 +8809,7 @@ Whether to ignore JAXBElement elements - only needed to be set to false in very
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether marhsalling must be java objects with JAXB annotations. And if not then it fails. This option can be set to
+Whether marshalling must be java objects with JAXB annotations. And if not then it fails. This option can be set to
false to relax that, such as when the data is already in XML format. Default value: false
]]>
</xs:documentation>
@@ -9389,7 +8819,7 @@ false to relax that, such as when the data is already in XML format. Default val
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To ignore non xml characheters and replace them with an empty space. Default value: false
+To ignore non xml characters and replace them with an empty space. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9407,10 +8837,8 @@ To overrule and use a specific encoding.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To turn on marshalling XML fragment trees. By default JAXB looks for XmlRootElement annotation on given class to operate
-on whole XML tree. This is useful but not always - sometimes generated code does not have XmlRootElement annotation,
-sometimes you need unmarshall only part of tree. In that case you can use partial unmarshalling. To enable this
-behaviours you need set property partClass. Camel will pass this class to JAXB's unmarshaler. Default value: false
+To turn on marshalling XML fragment trees. This is useful when generated code does not have XmlRootElement annotation
+and you need to unmarshall only part of the tree. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9419,7 +8847,7 @@ behaviours you need set property partClass. Camel will pass this class to JAXB's
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of class used for fragment parsing. See more details at the fragment option.
+Name of class used for fragment parsing.
]]>
</xs:documentation>
</xs:annotation>
@@ -9428,7 +8856,7 @@ Name of class used for fragment parsing. See more details at the fragment option
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-XML namespace to use for fragment parsing. See more details at the fragment option.
+XML namespace to use for fragment parsing.
]]>
</xs:documentation>
</xs:annotation>
@@ -9496,9 +8924,7 @@ value: true
<xs:documentation xml:lang="en">
<![CDATA[
Only in use if schema validation has been enabled. Restrict access to the protocols specified for external reference set
-by the schemaLocation attribute, Import and Include element. Examples of protocols are file, http, jar:file. empty,
-false or none to deny all access to external references; a specific protocol, such as file, to give permission to only
-the protocol; the keyword all to grant permission to all protocols.
+by the schemaLocation attribute, Import and Include element.
]]>
</xs:documentation>
</xs:annotation>
@@ -9588,7 +9014,7 @@ JSON views to accomplish this. This option is to refer to the class which has Js
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If you want to marshal a pojo to JSON, and the pojo has some fields with null values. And you want to skip these null
+If you want to marshal a POJO to JSON, and the POJO has some fields with null values. And you want to skip these null
values, you can set this option to NON_NULL.
]]>
</xs:documentation>
@@ -9646,10 +9072,8 @@ To use custom Jackson modules referred from the Camel registry. Multiple modules
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that
-matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. Multiple features can be separated
+by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -9658,10 +9082,8 @@ can be separated by comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name
-that matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. Multiple features can be
+separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -9680,8 +9102,7 @@ should only be enabled when desired to be used. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If set then Jackson will use the Timezone when marshalling/unmarshalling. This option will have no effect on the others
-Json DataFormat, like gson and fastjson.
+If set then Jackson will use the Timezone when marshalling/unmarshalling.
]]>
</xs:documentation>
</xs:annotation>
@@ -9738,10 +9159,7 @@ To configure the date format while marshall or unmarshall Date fields in JSON us
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Jackson. Sets the maximum string length (in chars or bytes, depending on input context). The default is 20,000,000. This
-limit is not exact, the limit is applied when we increase internal buffer sizes and an exception will happen at sizes
-greater than this limit. Some text values that are a little bigger than the limit may be treated as valid but no text
-values with sizes less than or equal to this limit will be treated as invalid.
+Sets the maximum string length (in chars or bytes, depending on input context). The default is 20,000,000.
]]>
</xs:documentation>
</xs:annotation>
@@ -9782,7 +9200,7 @@ The class to take into account while unmarshalling.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Enable encoding (compress) using multiple processing cores. Default value: false
+Whether to enable encoding (compress) using multiple processing cores. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9798,7 +9216,7 @@ Enable encoding (compress) using multiple processing cores. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Specify the subtype of the MIME Multipart. Default is mixed. Default value: mixed
+Specify the subtype of the MIME Multipart. Default value: mixed
]]>
</xs:documentation>
</xs:annotation>
@@ -9807,8 +9225,8 @@ Specify the subtype of the MIME Multipart. Default is mixed. Default value: mixe
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines whether a message without attachment is also marshaled into a MIME Multipart (with only one body part). Default
-is false. Default value: false
+Whether a message without attachment is also marshaled into a MIME Multipart (with only one body part). Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -9817,8 +9235,8 @@ is false. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines whether the MIME-Multipart headers are part of the message body (true) or are set as Camel headers (false).
-Default is false. Default value: false
+Whether the MIME-Multipart headers are part of the message body (true) or are set as Camel headers (false). Default
+value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9827,8 +9245,8 @@ Default is false. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A regex that defines which Camel headers are also included as MIME headers into the MIME multipart. This will only work
-if headersInline is set to true. Default is to include no headers.
+A regex that defines which Camel headers are also included as MIME headers into the MIME multipart. This only works if
+headersInline is set to true.
]]>
</xs:documentation>
</xs:annotation>
@@ -9837,8 +9255,8 @@ if headersInline is set to true. Default is to include no headers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines whether the content of binary parts in the MIME multipart is binary (true) or Base-64 encoded (false) Default is
-false. Default value: false
+Whether the content of binary parts in the MIME multipart is binary (true) or Base-64 encoded (false). Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -9881,8 +9299,8 @@ Class name of the OCSF event type to use when unmarshalling. Defaults to OcsfEve
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to
-use different collection types than java.util.Collection based as default.
+Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows using
+different collection types than java.util.Collection based as default.
]]>
</xs:documentation>
</xs:annotation>
@@ -9891,7 +9309,7 @@ use different collection types than java.util.Collection based as default.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To unmarshal to a List of OCSF events. Default value: false
+Whether to unmarshal to a List of OCSF events. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9900,8 +9318,7 @@ To unmarshal to a List of OCSF events. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If enabled then the unmarshal type can be specified via the CamelOcsfUnmarshalType header. This should only be enabled
-when desired to be used. Default value: false
+Whether to allow the unmarshal type to be specified via the CamelOcsfUnmarshalType header. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9910,7 +9327,7 @@ when desired to be used. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To enable pretty printing output nicely formatted. Is by default false. Default value: false
+Whether to enable pretty printing output nicely formatted. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -9935,7 +9352,7 @@ Compression codec to use when marshalling. Default value: GZIP
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Class to use when (un)marshalling. If omitted, parquet files are converted into Avro's GenericRecords for unmarshalling
+Class to use when (un)marshalling. If omitted, parquet files are converted into Avro GenericRecords for unmarshalling
and input objects are assumed as GenericRecords for marshalling.
]]>
</xs:documentation>
@@ -9946,6 +9363,212 @@ and input objects are assumed as GenericRecords for marshalling.
<xs:documentation xml:lang="en">
<![CDATA[
Whether the unmarshalling should produce an iterator of records or read all the records at once. Default value: false
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="pgpDataFormat">
+ <xs:complexContent>
+ <xs:extension base="tns:dataFormat">
+ <xs:sequence/>
+ <xs:attribute name="keyUserid" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The user ID of the key in the PGP keyring used during encryption. Can also be only a part of a user ID.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="signatureKeyUserid" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+User ID of the key in the PGP keyring used for signing (during encryption) or signature verification (during
+decryption).
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="password" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Password used when opening the private key (not used for encryption).
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="signaturePassword" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Password used when opening the private key used for signing (during encryption).
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="keyFileName" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Filename of the keyring; must be accessible as a classpath resource (but you can specify a location in the file system
+by using the file: prefix).
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="signatureKeyFileName" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Filename of the keyring to use for signing (during encryption) or for signature verification (during decryption); must
+be accessible as a classpath resource (but you can specify a location in the file system by using the file: prefix).
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="signatureKeyRing" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Keyring used for signing/verifying as byte array. You cannot set the signatureKeyFileName and signatureKeyRing at the
+same time.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="armored" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+This option will cause PGP to base64 encode the encrypted text, making it available for copy/paste, etc. Default value:
+false
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="integrity" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Adds an integrity check/sign into the encryption file. Default value: true
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="provider" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Java Cryptography Extension (JCE) provider, default is Bouncy Castle (BC). Alternatively you can use, for example, the
+IAIK JCE provider.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="algorithm" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Symmetric key encryption algorithm; possible values are defined in org.bouncycastle.bcpg.SymmetricKeyAlgorithmTags. Only
+relevant for encrypting.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="compressionAlgorithm" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Compression algorithm; possible values are defined in org.bouncycastle.bcpg.CompressionAlgorithmTags. Only relevant for
+encrypting.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="hashAlgorithm" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Signature hash algorithm; possible values are defined in org.bouncycastle.bcpg.HashAlgorithmTags. Only relevant for
+signing.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="signatureVerificationOption" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Controls the behavior for verifying the signature during unmarshaling. Possible values: optional, required, ignore,
+no_signature_allowed.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
+ <xs:complexType name="pqcDataFormat">
+ <xs:complexContent>
+ <xs:extension base="tns:dataFormat">
+ <xs:sequence/>
+ <xs:attribute name="keyEncapsulationAlgorithm" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The Post-Quantum KEM algorithm to use for key encapsulation. Default value: MLKEM
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="symmetricKeyAlgorithm" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The symmetric encryption algorithm to use with the shared secret. Only algorithms that support authenticated encryption
+(AEAD) are allowed: AES, ARIA, CAMELLIA, CAST6, DSTU7624, GOST3412_2015, SEED and SM4 are encrypted with GCM, and
+CHACHA7539 with ChaCha20-Poly1305. Default value: AES
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="symmetricKeyLength" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The length (in bits) of the symmetric key. Default value: 128
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="keyPair" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Refers to the KeyPair to lookup from the registry to use for KEM operations.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="provider" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The JCE security provider to use.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="keyGenerator" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Refers to a custom KeyGenerator to lookup from the registry for KEM operations.
]]>
</xs:documentation>
</xs:annotation>
@@ -10045,8 +9668,8 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows to
-use different collection types than java.util.Collection based as default.
+Refers to a custom collection type to lookup in the registry to use. This option should rarely be used, but allows using
+different collection types than java.util.Collection based as default.
]]>
</xs:documentation>
</xs:annotation>
@@ -10083,10 +9706,8 @@ To use custom Jackson modules referred from the Camel registry. Multiple modules
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name that
-matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to enable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. Multiple features can be separated
+by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -10095,10 +9716,8 @@ can be separated by comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. The features should be a name
-that matches a enum from com.fasterxml.jackson.databind.SerializationFeature,
-com.fasterxml.jackson.databind.DeserializationFeature, or com.fasterxml.jackson.databind.MapperFeature Multiple features
-can be separated by comma.
+Set of features to disable on the Jackson com.fasterxml.jackson.databind.ObjectMapper. Multiple features can be
+separated by comma.
]]>
</xs:documentation>
</xs:annotation>
@@ -10107,8 +9726,8 @@ can be separated by comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If enabled then Jackson is allowed to attempt to use the CamelJacksonUnmarshalType header during the unmarshalling. This
-should only be enabled when desired to be used. Default value: false
+If enabled then Jackson is allowed to attempt to use the CamelJacksonUnmarshalType header during the unmarshalling.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10145,8 +9764,7 @@ When not disabled, the SchemaResolver will be looked up into the registry. Defau
<xs:documentation xml:lang="en">
<![CDATA[
Defines a content type format in which protobuf message will be serialized/deserialized from(to) the Java been. The
-format can either be native or json for either native protobuf or json fields representation. The default value is
-native. Default value: native
+format can either be native or json for either native protobuf or json fields representation. Default value: native
]]>
</xs:documentation>
</xs:annotation>
@@ -10214,16 +9832,7 @@ To overrule and use a specific encoding.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to an element strategy to lookup from the registry. An element name strategy is used for two purposes. The first
-is to find a xml element name for a given object and soap action when marshaling the object into a SOAP message. The
-second is to find an Exception class for a given soap fault name. The following three element strategy class name is
-provided out of the box. QNameStrategy - Uses a fixed qName that is configured on instantiation. Exception lookup is not
-supported TypeNameStrategy - Uses the name and namespace from the XMLType annotation of the given type. If no namespace
-is set then package-info is used. Exception lookup is not supported ServiceInterfaceStrategy - Uses information from a
-webservice interface to determine the type name and to find the exception class for a SOAP fault All three classes is
-located in the package name org.apache.camel.dataformat.soap.name If you have generated the web service stub code with
-cxf-codegen or a similar tool then you probably will want to use the ServiceInterfaceStrategy. In the case you have no
-annotated service interface you should use QNameStrategy or TypeNameStrategy.
+Refers to an element strategy to lookup from the registry.
]]>
</xs:documentation>
</xs:annotation>
@@ -10241,8 +9850,8 @@ SOAP version should either be 1.1 or 1.2. Is by default 1.1. Default value: 1.1
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-When marshalling using JAXB or SOAP then the JAXB implementation will automatic assign namespace prefixes, such as ns2,
-ns3, ns4 etc. To control this mapping, Camel allows you to refer to a map which contains the desired mapping.
+When marshalling using JAXB or SOAP then the JAXB implementation will automatic assign namespace prefixes. To control
+this mapping, Camel allows you to refer to a map which contains the desired mapping.
]]>
</xs:documentation>
</xs:annotation>
@@ -10251,7 +9860,7 @@ ns3, ns4 etc. To control this mapping, Camel allows you to refer to a map which
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To validate against an existing schema. Your can use the prefix classpath:, file: or http: to specify how the resource
+To validate against an existing schema. You can use the prefix classpath:, file: or http: to specify how the resource
should be resolved. You can separate multiple schema files by using the ',' character.
]]>
</xs:documentation>
@@ -10261,9 +9870,7 @@ should be resolved. You can separate multiple schema files by using the ',' char
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to ignore headers that was not unmarshalled. By default, headers which could not be unmarshalled is recorded in
-the org.apache.camel.dataformat.soap.UNMARSHALLED_HEADER_LIST header which allows to inspect any problematic header.
-Default value: false
+Whether to ignore headers that were not unmarshalled. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10279,7 +9886,7 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The flag indicating that messages must be marshalled in a JSON format. Default value: false
+Whether to marshal messages in JSON format. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10295,7 +9902,7 @@ The flag indicating that messages must be marshalled in a JSON format. Default v
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The flag indicating that messages must be marshalled in a JSON format. Default value: false
+Whether to marshal messages in JSON format. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10346,8 +9953,8 @@ Refers to a specific configuration to use when marshalling a message to lookup f
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If the tar file has more than one entry, the setting this option to true, allows working with the splitter EIP, to split
-the data using an iterator in a streaming mode. Default value: false
+Whether to use an iterator to split tar entries when the tar file has more than one entry, for use with the splitter EIP
+in streaming mode. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10356,8 +9963,8 @@ the data using an iterator in a streaming mode. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If the tar file has more than one entry, setting this option to true, allows to get the iterator even if the directory
-is empty. Default value: false
+Whether to allow getting the iterator even if the directory is empty, when the tar file has more than one entry. Default
+value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10366,8 +9973,7 @@ is empty. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If the file name contains path elements, setting this option to true, allows the path to be maintained in the tar file.
-Default value: false
+Whether to preserve path elements when the file name contains path elements in the tar file. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10376,9 +9982,8 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set the maximum decompressed size of a tar file (in bytes). The default value if not specified corresponds to 1
-gigabyte. An IOException will be thrown if the decompressed size exceeds this amount. Set to -1 to disable setting a
-maximum decompressed size. Default value: 1073741824
+The maximum decompressed size of a tar file (in bytes). An IOException is thrown if the decompressed size exceeds this
+amount. Set to -1 to disable. Default value: 1073741824
]]>
</xs:documentation>
</xs:annotation>
@@ -10403,9 +10008,8 @@ Name of class to use when unmarshalling.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Defines a content type format in which thrift message will be serialized/deserialized from(to) the Java been. The format
-can either be native or json for either native binary thrift, json or simple json fields representation. The default
-value is binary. Default value: binary
+The content type format in which thrift message will be serialized/deserialized. The format can be native binary, json,
+or simple json. Default value: binary
]]>
</xs:documentation>
</xs:annotation>
@@ -10477,7 +10081,7 @@ The quote escape symbol. Default value: "
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The string representation of a null value. The default value is null.
+The string representation of a null value.
]]>
</xs:documentation>
</xs:annotation>
@@ -10486,7 +10090,7 @@ The string representation of a null value. The default value is null.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the empty lines must be ignored. The default value is true. Default value: true
+Whether or not the empty lines must be ignored. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -10495,7 +10099,7 @@ Whether or not the empty lines must be ignored. The default value is true. Defau
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the trailing white spaces must be ignored. The default value is true. Default value: true
+Whether or not the trailing white spaces must be ignored. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -10504,7 +10108,7 @@ Whether or not the trailing white spaces must be ignored. The default value is t
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the leading white spaces must be ignored. The default value is true. Default value: true
+Whether or not the leading white spaces must be ignored. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -10514,7 +10118,7 @@ Whether or not the leading white spaces must be ignored. The default value is tr
<xs:documentation xml:lang="en">
<![CDATA[
Whether or not the headers are disabled. When defined, this option explicitly sets the headers as null which indicates
-that there is no header. The default value is false. Default value: false
+that there is no header. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10523,8 +10127,7 @@ that there is no header. The default value is false. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the header must be read in the first line of the test document. The default value is false. Default
-value: false
+Whether or not the header must be read in the first line of the test document. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10569,7 +10172,7 @@ The normalized line separator of the files. The default value is a new line char
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The comment symbol. The default value is #. Default value: #
+The comment symbol. Default value: #
]]>
</xs:documentation>
</xs:annotation>
@@ -10579,7 +10182,7 @@ The comment symbol. The default value is #. Default value: #
<xs:documentation xml:lang="en">
<![CDATA[
Whether the unmarshalling should produce an iterator that reads the lines on the fly or if all the lines must be read at
-once. The default value is false. Default value: false
+once. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10589,7 +10192,7 @@ once. The default value is false. Default value: false
<xs:documentation xml:lang="en">
<![CDATA[
Whether the unmarshalling should produce maps for the lines values instead of lists. It requires to have header (either
-defined or collected). The default value is false. Default value: false
+defined or collected). Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10629,7 +10232,7 @@ The padding character. The default value is a space.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the trailing characters until new line must be ignored. The default value is false. Default value: false
+Whether to skip trailing characters until a new line is found. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10638,7 +10241,7 @@ Whether or not the trailing characters until new line must be ignored. The defau
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the record ends on new line. The default value is false. Default value: false
+Whether the record ends on a new line. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10670,10 +10273,7 @@ The escape character. Default value: \
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The cipher algorithm to be used for encryption/decryption of the XML message content. The available choices are:
-XMLCipher.TRIPLEDES XMLCipher.AES_128 XMLCipher.AES_128_GCM XMLCipher.AES_192 XMLCipher.AES_192_GCM XMLCipher.AES_256
-XMLCipher.AES_256_GCM XMLCipher.SEED_128 XMLCipher.CAMELLIA_128 XMLCipher.CAMELLIA_192 XMLCipher.CAMELLIA_256 The
-default value is XMLCipher.AES_256_GCM. Default value: AES-256-GCM
+The cipher algorithm to be used for encryption/decryption of the XML message content. Default value: AES-256-GCM
]]>
</xs:documentation>
</xs:annotation>
@@ -10682,9 +10282,7 @@ default value is XMLCipher.AES_256_GCM. Default value: AES-256-GCM
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A String used as passPhrase to encrypt/decrypt content. The passPhrase has to be provided. The passPhrase needs to be
-put together in conjunction with the appropriate encryption algorithm. For example using TRIPLEDES the passPhase can be
-a Only another 24 Byte key.
+A String used as passPhrase to encrypt/decrypt content.
]]>
</xs:documentation>
</xs:annotation>
@@ -10693,9 +10291,7 @@ a Only another 24 Byte key.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A byte used as passPhrase to encrypt/decrypt content. The passPhrase has to be provided. The passPhrase needs to be put
-together in conjunction with the appropriate encryption algorithm. For example using TRIPLEDES the passPhase can be a
-Only another 24 Byte key.
+A byte used as passPhrase to encrypt/decrypt content.
]]>
</xs:documentation>
</xs:annotation>
@@ -10715,7 +10311,7 @@ encrypted/decrypted.
<xs:documentation xml:lang="en">
<![CDATA[
A boolean value to specify whether the XML Element is to be encrypted or the contents of the XML Element. false =
-Element Level. true = Element Content Level. Default value: false
+Element Level, true = Element Content Level. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -10724,9 +10320,7 @@ Element Level. true = Element Content Level. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The cipher algorithm to be used for encryption/decryption of the asymmetric key. The available choices are:
-XMLCipher.RSA_v1dot5 XMLCipher.RSA_OAEP XMLCipher.RSA_OAEP_11 The default value is XMLCipher.RSA_OAEP. Default value:
-RSA_OAEP
+The cipher algorithm to be used for encryption/decryption of the asymmetric key. Default value: RSA_OAEP
]]>
</xs:documentation>
</xs:annotation>
@@ -10764,8 +10358,7 @@ The password to be used for retrieving the private key from the KeyStore. This k
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The digest algorithm to use with the RSA OAEP algorithm. The available choices are: XMLCipher.SHA1 XMLCipher.SHA256
-XMLCipher.SHA512 The default value is XMLCipher.SHA1. Default value: SHA1
+The digest algorithm to use with the RSA OAEP algorithm. Default value: SHA1
]]>
</xs:documentation>
</xs:annotation>
@@ -10774,9 +10367,7 @@ XMLCipher.SHA512 The default value is XMLCipher.SHA1. Default value: SHA1
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The MGF Algorithm to use with the RSA OAEP algorithm. The available choices are: EncryptionConstants.MGF1_SHA1
-EncryptionConstants.MGF1_SHA256 EncryptionConstants.MGF1_SHA512 The default value is EncryptionConstants.MGF1_SHA1.
-Default value: MGF1_SHA1
+The MGF Algorithm to use with the RSA OAEP algorithm. Default value: MGF1_SHA1
]]>
</xs:documentation>
</xs:annotation>
@@ -10795,231 +10386,7 @@ Default value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a Map XML Namespaces of prefix - uri mappings.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="pgpDataFormat">
- <xs:complexContent>
- <xs:extension base="tns:dataFormat">
- <xs:sequence/>
- <xs:attribute name="keyUserid" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The user ID of the key in the PGP keyring used during encryption. Can also be only a part of a user ID. For example, if
-the user ID is Test User then you can use the part Test User or to address the user ID.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="signatureKeyUserid" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-User ID of the key in the PGP keyring used for signing (during encryption) or signature verification (during
-decryption). During the signature verification process the specified User ID restricts the public keys from the public
-keyring which can be used for the verification. If no User ID is specified for the signature verficiation then any
-public key in the public keyring can be used for the verification. Can also be only a part of a user ID. For example, if
-the user ID is Test User then you can use the part Test User or to address the User ID.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="password" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Password used when opening the private key (not used for encryption).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="signaturePassword" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Password used when opening the private key used for signing (during encryption).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="keyFileName" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Filename of the keyring; must be accessible as a classpath resource (but you can specify a location in the file system
-by using the file: prefix).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="signatureKeyFileName" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Filename of the keyring to use for signing (during encryption) or for signature verification (during decryption); must
-be accessible as a classpath resource (but you can specify a location in the file system by using the file: prefix).
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="signatureKeyRing" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Keyring used for signing/verifying as byte array. You can not set the signatureKeyFileName and signatureKeyRing at the
-same time.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="armored" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-This option will cause PGP to base64 encode the encrypted text, making it available for copy/paste, etc. Default value:
-false
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="integrity" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Adds an integrity check/sign into the encryption file. The default value is true. Default value: true
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="provider" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Java Cryptography Extension (JCE) provider, default is Bouncy Castle (BC). Alternatively you can use, for example, the
-IAIK JCE provider; in this case the provider must be registered beforehand and the Bouncy Castle provider must not be
-registered beforehand. The Sun JCE provider does not work.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="algorithm" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Symmetric key encryption algorithm; possible values are defined in org.bouncycastle.bcpg.SymmetricKeyAlgorithmTags; for
-example 2 (= TRIPLE DES), 3 (= CAST5), 4 (= BLOWFISH), 6 (= DES), 7 (= AES_128). Only relevant for encrypting.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="compressionAlgorithm" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Compression algorithm; possible values are defined in org.bouncycastle.bcpg.CompressionAlgorithmTags; for example 0 (=
-UNCOMPRESSED), 1 (= ZIP), 2 (= ZLIB), 3 (= BZIP2). Only relevant for encrypting.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="hashAlgorithm" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Signature hash algorithm; possible values are defined in org.bouncycastle.bcpg.HashAlgorithmTags; for example 2 (=
-SHA1), 8 (= SHA256), 9 (= SHA384), 10 (= SHA512), 11 (=SHA224). Only relevant for signing.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="signatureVerificationOption" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Controls the behavior for verifying the signature during unmarshaling. There are 4 values possible: optional: The PGP
-message may or may not contain signatures; if it does contain signatures, then a signature verification is executed.
-required: The PGP message must contain at least one signature; if this is not the case an exception (PGPException) is
-thrown. A signature verification is executed. ignore: Contained signatures in the PGP message are ignored; no signature
-verification is executed. no_signature_allowed: The PGP message must not contain a signature; otherwise an exception
-(PGPException) is thrown.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="pqcDataFormat">
- <xs:complexContent>
- <xs:extension base="tns:dataFormat">
- <xs:sequence/>
- <xs:attribute name="keyEncapsulationAlgorithm" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The Post-Quantum KEM algorithm to use for key encapsulation. Supported values: MLKEM, BIKE, HQC, CMCE, SABER, FRODO,
-NTRU, NTRULPRime, SNTRUPrime, KYBER. Default value: MLKEM
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="symmetricKeyAlgorithm" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The symmetric encryption algorithm to use with the shared secret. Supported values: AES, ARIA, RC2, RC5, CAMELLIA,
-CAST5, CAST6, CHACHA7539, etc. Default value: AES
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="symmetricKeyLength" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The length (in bits) of the symmetric key. Default value: 128
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="keyPair" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Refers to the KeyPair to lookup from the register to use for KEM operations.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="bufferSize" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The size of the buffer used for streaming encryption/decryption. Default value: 4096
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="provider" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The JCE security provider to use.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:attribute>
- <xs:attribute name="keyGenerator" type="xs:string">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Refers to a custom KeyGenerator to lookup from the register for KEM operations.
+Refers to a Map of XML Namespaces of prefix to uri mappings.
]]>
</xs:documentation>
</xs:annotation>
@@ -11150,8 +10517,8 @@ Set whether recursive keys are allowed. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To specify a specific compression between 0-9. -1 is default compression, 0 is no compression, and 9 is the best
-compression. Default value: -1
+Compression level to use (0-9). -1 is default compression, 0 is no compression, and 9 is the best compression. Default
+value: -1
]]>
</xs:documentation>
</xs:annotation>
@@ -11198,8 +10565,7 @@ Default value: false
<xs:documentation xml:lang="en">
<![CDATA[
Set the maximum decompressed size of a zip file (in bytes). The default value if not specified corresponds to 1
-gigabyte. An IOException will be thrown if the decompressed size exceeds this amount. Set to -1 to disable setting a
-maximum decompressed size. Default value: 1073741824
+gigabyte. Set to -1 to disable setting a maximum decompressed size. Default value: 1073741824
]]>
</xs:documentation>
</xs:annotation>
@@ -11215,6 +10581,7 @@ maximum decompressed size. Default value: 1073741824
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -11285,16 +10652,14 @@ maximum decompressed size. Default value: 1073741824
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="aggregationStrategy" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to an AggregationStrategy to be used to assemble the replies from the multicasts, into a single outgoing message
-from the Multicast. By default Camel will use the last reply as the outgoing message. You can also use a POJO as the
-AggregationStrategy.
+Reference to the AggregationStrategy to assemble the replies from the multicasts into a single outgoing message. By
+default Camel uses the last reply as the outgoing message.
]]>
</xs:documentation>
</xs:annotation>
@@ -11303,7 +10668,7 @@ AggregationStrategy.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-This option can be used to explicit declare the method name to use, when using POJOs as the AggregationStrategy.
+The method name to use when using a POJO as the AggregationStrategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -11312,9 +10677,8 @@ This option can be used to explicit declare the method name to use, when using P
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If this option is false then the aggregate method is not used if there was no data to enrich. If this option is true
-then null values is used as the oldExchange (when no data to enrich), when using POJOs as the AggregationStrategy.
-Default value: false
+If true then null is used as the oldExchange when there is no data to aggregate, when using POJOs as the
+AggregationStrategy. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11335,15 +10699,8 @@ higher performance when the AggregationStrategy is implemented as thread-safe. D
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If enabled then sending messages to the multicasts occurs concurrently. Note the caller thread will still wait until all
-messages has been fully processed, before it continues. Its only the sending and processing the replies from the
-multicasts which happens concurrently. When parallel processing is enabled, then the Camel routing engin will continue
-processing using last used thread from the parallel thread pool. However, if you want to use the original thread that
-called the multicast, then make sure to enable the synchronous option as well. In parallel processing mode, you may want
-to also synchronous = true to force this EIP to process the sub-tasks using the upper bounds of the thread-pool. If
-using synchronous = false then Camel will allow its reactive routing engine to use as many threads as possible, which
-may be available due to sub-tasks using other thread-pools such as CompletableFuture.runAsync or others. Default value:
-false
+If enabled then sending messages to the multicasts occurs concurrently. The caller thread still waits until all messages
+are fully processed before it continues. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11352,8 +10709,8 @@ false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether synchronous processing should be strictly used. When enabled then the same thread is used to continue
-routing after the multicast is complete, even if parallel processing is enabled. Default value: false
+When enabled then the same thread is used to continue routing after the multicast is complete, even if parallel
+processing is enabled. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11362,7 +10719,7 @@ routing after the multicast is complete, even if parallel processing is enabled.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If enabled then Camel will process replies out-of-order, eg in the order they come back. If disabled, Camel will process
+If enabled then Camel will process replies out-of-order, in the order they come back. If disabled, Camel will process
replies in the same order as defined by the multicast. Default value: false
]]>
</xs:documentation>
@@ -11372,11 +10729,9 @@ replies in the same order as defined by the multicast. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will now stop further processing if an exception or failure occurred during processing of an org.apache.camel.Exchange
-and the caused exception will be thrown. Will also stop if processing the exchange failed (has a fault message) or an
-exception was thrown and handled by the error handler (such as using onException). In all situations the multicast will
-stop further processing. This is the same behavior as in pipeline, which is used by the routing engine. The default
-behavior is to not stop but continue processing till the end. Default value: false
+If enabled then stops further multicast processing if an exception or failure occurred during processing of an exchange,
+and the caused exception will be thrown. The default behavior is to not stop but continue processing till the end.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11385,11 +10740,8 @@ behavior is to not stop but continue processing till the end. Default value: fal
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a total timeout specified in millis, when using parallel processing. If the Multicast hasn't been able to send and
-process all replies within the given timeframe, then the timeout triggers and the Multicast breaks out and continues.
-The timeout method is invoked before breaking out. If the timeout is reached with running tasks still remaining, certain
-tasks for which it is difficult for Camel to shut down in a graceful manner may continue to run. So use this option with
-a bit of care. Default value: 0
+Total timeout in millis when using parallel processing. If the multicast has not been able to process all replies within
+the given timeframe, then the timeout triggers and the multicast breaks out and continues. Default value: 0
]]>
</xs:documentation>
</xs:annotation>
@@ -11398,8 +10750,7 @@ a bit of care. Default value: 0
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Refers to a custom Thread Pool to be used for parallel processing. Notice if you set this option, then parallel
-processing is automatic implied, and you do not have to enable that option as well.
+Reference to a custom thread pool to use for parallel processing. Setting this option implies parallel processing.
]]>
</xs:documentation>
</xs:annotation>
@@ -11408,8 +10759,7 @@ processing is automatic implied, and you do not have to enable that option as we
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Uses the Processor when preparing the org.apache.camel.Exchange to be send. This can be used to deep-clone messages that
-should be send, or any custom logic needed before the exchange is send.
+Reference to a processor for preparing the exchange to be sent. Can be used to deep-clone messages that should be sent.
]]>
</xs:documentation>
</xs:annotation>
@@ -11418,9 +10768,8 @@ should be send, or any custom logic needed before the exchange is send.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Shares the org.apache.camel.spi.UnitOfWork with the parent and each of the sub messages. Multicast will by default not
-share unit of work between the parent exchange and each multicasted exchange. This means each sub exchange has its own
-individual unit of work. Default value: false
+Shares the unit of work with the parent and each of the multicast exchanges. By default each multicast exchange has its
+own individual unit of work. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11434,6 +10783,7 @@ individual unit of work. Default value: false
<xs:sequence>
<xs:element minOccurs="0" ref="tns:onWhen"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -11504,14 +10854,15 @@ individual unit of work. Default value: false
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="mode" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the on completion mode. The default value is AfterConsumer. Default value: AfterConsumer
+Controls when the on-completion callback runs. AfterConsumer (default) runs after the consumer has written the response
+back to the caller. BeforeConsumer runs before the consumer writes the response, allowing the on-completion route to
+modify the Exchange before it is returned to the caller (e.g. in InOut mode). Default value: AfterConsumer
]]>
</xs:documentation>
</xs:annotation>
@@ -11520,7 +10871,7 @@ Sets the on completion mode. The default value is AfterConsumer. Default value:
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will only synchronize when the org.apache.camel.Exchange completed successfully (no errors). Default value: false
+Will only synchronize when the Exchange completed successfully (no errors). Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11529,8 +10880,7 @@ Will only synchronize when the org.apache.camel.Exchange completed successfully
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will only synchronize when the org.apache.camel.Exchange ended with failure (exception or FAULT message). Default value:
-false
+Will only synchronize when the Exchange ended with failure (exception or FAULT message). Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11550,8 +10900,8 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom Thread Pool to be used for parallel processing. Notice if you set this option, then parallel processing
-is automatic implied, and you do not have to enable that option as well.
+Refers to a custom Thread Pool to be used for parallel processing. Notice if you set this option, then parallel
+processing is automatically implied, and you do not have to enable that option as well.
]]>
</xs:documentation>
</xs:annotation>
@@ -11560,19 +10910,8 @@ is automatic implied, and you do not have to enable that option as well.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will use the original input message body when an org.apache.camel.Exchange for this on completion. The original input
-message is defensively copied, and the copied message body is converted to org.apache.camel.StreamCache if possible
-(stream caching is enabled, can be disabled globally or on the original route), to ensure the body can be read when the
-original message is being used later. If the body is converted to org.apache.camel.StreamCache then the message body on
-the current org.apache.camel.Exchange is replaced with the org.apache.camel.StreamCache body. If the body is not
-converted to org.apache.camel.StreamCache then the body will not be able to re-read when accessed later. Important: The
-original input means the input message that are bounded by the current org.apache.camel.spi.UnitOfWork . An unit of work
-typically spans one route, or multiple routes if they are connected using internal endpoints such as direct or seda.
-When messages is passed via external endpoints such as JMS or HTTP then the consumer will create a new unit of work,
-with the message it received as input as the original input. Also some EIP patterns such as splitter, multicast, will
-create a new unit of work boundary for the messages in their sub-route (eg the split message); however these EIPs have
-an option named shareUnitOfWork which allows to combine with the parent unit of work in regard to error handling and
-therefore use the parent original message. By default this feature is off. Default value: false
+Will use the original input message when an Exchange for this on completion. By default this feature is off. Default
+value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11588,7 +10927,7 @@ therefore use the parent original message. By default this feature is off. Defau
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-A set of exceptions to react upon.
+A list of exception class names to catch and handle.
]]>
</xs:documentation>
</xs:annotation>
@@ -11598,7 +10937,8 @@ A set of exceptions to react upon.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the retry while predicate. Will continue retrying until predicate returns false.
+Sets a predicate to control whether redelivery should continue. Redelivery continues as long as the predicate evaluates
+to true.
]]>
</xs:documentation>
</xs:annotation>
@@ -11608,7 +10948,10 @@ Sets the retry while predicate. Will continue retrying until predicate returns f
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether the exchange should be marked as handled or not.
+When handled is set to true, the exception is suppressed and not sent back to the caller. The original route stops at
+the point of failure and only the steps in this onException block execute. The response returned to the caller is
+whatever this onException block produces. Use continued instead if you want to resume the original route from the point
+of failure.
]]>
</xs:documentation>
</xs:annotation>
@@ -11617,13 +10960,15 @@ Sets whether the exchange should be marked as handled or not.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether the exchange should handle and continue routing from the point of failure. If this option is enabled then
-its considered handled as well.
+When continued is set to true, the exception is handled and routing continues from the point of failure. Unlike handled,
+which stops the original route and only runs the onException block, continued resumes the original route after the
+onException steps complete. The exception is considered handled as well.
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -11694,14 +11039,13 @@ its considered handled as well.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="redeliveryPolicyRef" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a redelivery policy to lookup in the org.apache.camel.spi.Registry to be used.
+Sets a reference to a redelivery policy to lookup in the registry to be used.
]]>
</xs:documentation>
</xs:annotation>
@@ -11710,8 +11054,8 @@ Sets a reference to a redelivery policy to lookup in the org.apache.camel.spi.Re
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a processor that should be processed before a redelivery attempt. Can be used to change the
-org.apache.camel.Exchange before its being redelivered.
+Sets a reference to a processor that is invoked before each redelivery attempt. Can be used to change the exchange
+before it is redelivered.
]]>
</xs:documentation>
</xs:annotation>
@@ -11720,9 +11064,8 @@ org.apache.camel.Exchange before its being redelivered.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to a processor that should be processed just after an exception occurred. Can be used to perform custom
-logging about the occurred exception at the exact time it happened. Important: Any exception thrown from this processor
-will be ignored.
+Sets a reference to a processor that is invoked just after an exception occurred. Can be used to perform custom logging.
+Any exception thrown from this processor is ignored.
]]>
</xs:documentation>
</xs:annotation>
@@ -11731,30 +11074,8 @@ will be ignored.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will use the original input org.apache.camel.Message (original body and headers) when an org.apache.camel.Exchange is
-moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the
-org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN
-message we use the original IN message instead. This allows you to store the original input in the dead letter queue
-instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and
-then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the
-org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send
-the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that
-the former includes both the original body and headers, where as the latter only includes the original body. You can use
-the latter to enrich the message with custom headers and include the original message body. The former wont let you do
-this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and
-useOriginalBody. The original input message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route),
-to ensure the body can be read when the original message is being used later. If the body is converted to
-org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the
-org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not
-be able to re-read when accessed later. Important: The original input means the input message that are bounded by the
-current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are
-connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or
-HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also
-some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their
-sub-route (eg the split message); however these EIPs have an option named shareUnitOfWork which allows to combine with
-the parent unit of work in regard to error handling and therefore use the parent original message. By default this
-feature is off. Default value: false
+If enabled, uses the original input message (body and headers) when the exchange is moved to the dead letter queue after
+all redelivery attempts have been exhausted. Cannot be used together with useOriginalBody. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11763,30 +11084,9 @@ feature is off. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will use the original input org.apache.camel.Message body (original body only) when an org.apache.camel.Exchange is
-moved to the dead letter queue. Notice: this only applies when all redeliveries attempt have failed and the
-org.apache.camel.Exchange is doomed for failure. Instead of using the current inprogress org.apache.camel.Exchange IN
-message we use the original IN message instead. This allows you to store the original input in the dead letter queue
-instead of the inprogress snapshot of the IN message. For instance if you route transform the IN body during routing and
-then failed. With the original exchange store in the dead letter queue it might be easier to manually re submit the
-org.apache.camel.Exchange again as the IN message is the same as when Camel received it. So you should be able to send
-the org.apache.camel.Exchange to the same input. The difference between useOriginalMessage and useOriginalBody is that
-the former includes both the original body and headers, where as the latter only includes the original body. You can use
-the latter to enrich the message with custom headers and include the original message body. The former wont let you do
-this, as its using the original message body and headers as they are. You cannot enable both useOriginalMessage and
-useOriginalBody. The original input message is defensively copied, and the copied message body is converted to
-org.apache.camel.StreamCache if possible (stream caching is enabled, can be disabled globally or on the original route),
-to ensure the body can be read when the original message is being used later. If the body is converted to
-org.apache.camel.StreamCache then the message body on the current org.apache.camel.Exchange is replaced with the
-org.apache.camel.StreamCache body. If the body is not converted to org.apache.camel.StreamCache then the body will not
-be able to re-read when accessed later. Important: The original input means the input message that are bounded by the
-current org.apache.camel.spi.UnitOfWork . An unit of work typically spans one route, or multiple routes if they are
-connected using internal endpoints such as direct or seda. When messages is passed via external endpoints such as JMS or
-HTTP then the consumer will create a new unit of work, with the message it received as input as the original input. Also
-some EIP patterns such as splitter, multicast, will create a new unit of work boundary for the messages in their
-sub-route (eg the split message); however these EIPs have an option named shareUnitOfWork which allows to combine with
-the parent unit of work in regard to error handling and therefore use the parent original message. By default this
-feature is off. Default value: false
+If enabled, uses the original input message body (but not headers) when the exchange is moved to the dead letter queue
+after all redelivery attempts have been exhausted. This allows enriching the message with custom headers while keeping
+the original body. Cannot be used together with useOriginalMessage. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11802,7 +11102,7 @@ feature is off. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set output type URN.
+The output type URN, such as java:fully.qualified.ClassName or json:SchemaName.
]]>
</xs:documentation>
</xs:annotation>
@@ -11811,7 +11111,7 @@ Set output type URN.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether if validation is required for this output type. Default value: false
+Whether to validate the output type. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -11825,7 +11125,7 @@ Whether if validation is required for this output type. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the java package names to use for scanning for route builder classes.
+Java package names to use for scanning for route builder classes.
]]>
</xs:documentation>
</xs:annotation>
@@ -11858,7 +11158,7 @@ Include finding route builder from these java package names.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the consumer listener to use.
+The consumer listener to use for pausing and resuming the consumer.
]]>
</xs:documentation>
</xs:annotation>
@@ -11867,10 +11167,7 @@ Sets the consumer listener to use.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-References to a java.util.function.Predicate to use for until checks. The predicate is responsible for evaluating
-whether the processing can resume or not. Such predicate should return true if the consumption can resume, or false
-otherwise. The exact point of when the predicate is called is dependent on the component, and it may be called on either
-one of the available events. Implementations should not assume the predicate to be called at any specific point.
+Predicate to evaluate whether the processing can resume. Returns true if consumption can resume, or false otherwise.
]]>
</xs:documentation>
</xs:annotation>
@@ -11883,6 +11180,7 @@ one of the available events. Implementations should not assume the predicate to
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -11953,7 +11251,6 @@ one of the available events. Implementations should not assume the predicate to
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -11964,6 +11261,7 @@ one of the available events. Implementations should not assume the predicate to
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -12034,14 +11332,13 @@ one of the available events. Implementations should not assume the predicate to
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="ref" type="xs:string" use="required">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to use for lookup the policy in the registry.
+Reference to the policy to lookup in the registry.
]]>
</xs:documentation>
</xs:annotation>
@@ -12058,8 +11355,7 @@ Sets a reference to use for lookup the policy in the registry.
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
-user data and to easily control what data to use for sending and receiving. Important: When using receive variable then
-the received body is stored only in this variable and not on the current message.
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -12068,7 +11364,8 @@ the received body is stored only in this variable and not on the current message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the uri of the endpoint to poll from.
+The uri of the endpoint to poll a single message from. The result is stored in the original message body (or in a
+variable if variableReceive is set).
]]>
</xs:documentation>
</xs:annotation>
@@ -12077,12 +11374,7 @@ Sets the uri of the endpoint to poll from.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Timeout in millis when polling from the external service. The timeout has influence about the poll enrich behavior. It
-basically operations in three different modes: negative value - Waits until a message is available and then returns it.
-Warning that this method could block indefinitely if no messages are available. 0 - Attempts to receive a message
-exchange immediately without waiting and returning null if a message exchange is not available yet. positive value -
-Attempts to receive a message exchange, waiting up to the given timeout to expire if a message is not yet available.
-Returns null if timed out The default value is 20000 (20 seconds). Default value: 20000
+Timeout in millis when polling from the external service. The default value is 20000 (20 seconds). Default value: 20000
]]>
</xs:documentation>
</xs:annotation>
@@ -12102,6 +11394,7 @@ Returns null if timed out The default value is 20000 (20 seconds). Default value
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -12127,8 +11420,7 @@ Returns null if timed out The default value is 20000 (20 seconds). Default value
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
-user data and to easily control what data to use for sending and receiving. Important: When using receive variable then
-the received body is stored only in this variable and not on the current message.
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -12147,7 +11439,7 @@ default Camel will use the reply from the external service as outgoing message.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-This option can be used to explicit declare the method name to use, when using POJOs as the AggregationStrategy.
+This option can be used to explicitly declare the method name to use, when using POJOs as the AggregationStrategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -12168,8 +11460,7 @@ then null values is used as the oldExchange (when no data to enrich), when using
<![CDATA[
If this option is false then the aggregate method is not used if there was an exception thrown while trying to retrieve
the data to enrich from the resource. Setting this option to true allows end users to control what to do if there was an
-exception in the aggregate method. For example to suppress the exception or set a custom message body etc. Default
-value: false
+exception in the aggregate method. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -12178,13 +11469,9 @@ value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Timeout in millis when polling from the external service. The timeout has influence about the poll enrich behavior. It
-basically operations in three different modes: negative value - Waits until a message is available and then returns it.
-Warning that this method could block indefinitely if no messages are available. 0 - Attempts to receive a message
-exchange immediately without waiting and returning null if a message exchange is not available yet. positive value -
-Attempts to receive a message exchange, waiting up to the given timeout to expire if a message is not yet available.
-Returns null if timed out The default value is -1 and therefore the method could block indefinitely, and therefore its
-recommended to use a timeout value. Default value: -1
+Timeout in millis when polling from the external service. A negative value waits until a message is available (could
+block indefinitely). Zero attempts to receive immediately without waiting. A positive value waits up to the given
+timeout. Default value: -1
]]>
</xs:documentation>
</xs:annotation>
@@ -12193,15 +11480,8 @@ recommended to use a timeout value. Default value: -1
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum size used by the org.apache.camel.spi.ConsumerCache which is used to cache and reuse consumers when
-uris are reused. Beware that when using dynamic endpoints then it affects how well the cache can be utilized. If each
-dynamic endpoint is unique then its best to turn off caching by setting this to -1, which allows Camel to not cache both
-the consumers and endpoints; they are regarded as prototype scoped and will be stopped and discarded after use. This
-reduces memory usage as otherwise consumers/endpoints are stored in memory in the caches. However, if there are a high
-degree of dynamic endpoints that have been used before, then it can benefit to use the cache to reuse both consumers and
-endpoints and therefore the cache size can be set accordingly or rely on the default size (1000). If there is a mix of
-unique and used before dynamic endpoints, then setting a reasonable cache size can help reduce memory usage to avoid
-storing too many non-frequent used consumers.
+Sets the maximum size used by the ConsumerCache which is used to cache and reuse consumers when uris are reused. Use 0
+for default cache size, or -1 to turn cache off.
]]>
</xs:documentation>
</xs:annotation>
@@ -12210,7 +11490,7 @@ storing too many non-frequent used consumers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Ignore the invalidate endpoint exception when try to create a consumer with that endpoint. Default value: false
+Whether to ignore an invalid endpoint URI when trying to create a consumer with that endpoint. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -12219,7 +11499,7 @@ Ignore the invalidate endpoint exception when try to create a consumer with that
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to allow components to optimise if they are org.apache.camel.spi.PollDynamicAware. Default value: true
+Whether to allow components to optimise if they are PollDynamicAware. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -12229,6 +11509,17 @@ Whether to allow components to optimise if they are org.apache.camel.spi.PollDyn
<xs:documentation xml:lang="en">
<![CDATA[
Whether to auto startup components when poll enricher is starting up. Default value: true
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="allowedSchemes" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets an optional comma-separated allow-list of component schemes that the dynamic recipient may resolve to (e.g.
+http,https). When set, a dynamic endpoint whose scheme is not in the list is rejected. This is a defence-in-depth
+restriction, useful for low-code / Kamelet deployments; by default (unset) any scheme is allowed.
]]>
</xs:documentation>
</xs:annotation>
@@ -12244,13 +11535,8 @@ Whether to auto startup components when poll enricher is starting up. Default va
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to the Processor to lookup in the registry to use. A Processor is a class of type org.apache.camel.Processor,
-which can are to be called by this EIP. In this processor you have custom Java code, that can work with the message,
-such as to do custom business logic, special message manipulations and so on. By default, the ref, will lookup the bean
-in the Camel registry. The ref can use prefix that controls how the processor is obtained. You can use #bean:myBean
-where myBean is the id of the Camel processor (lookup). Can also be used for creating new beans by their class name by
-prefixing with #class, eg #class:com.foo.MyClassType. And it is also possible to refer to singleton beans by their type
-in the registry by prefixing with #type: syntax, eg #type:com.foo.MyClassType.
+Reference to the Processor to lookup in the registry to use. Can use prefixes such as #bean:, #class:, or #type: to
+control how the processor is obtained.
]]>
</xs:documentation>
</xs:annotation>
@@ -12273,6 +11559,7 @@ in the registry by prefixing with #type: syntax, eg #type:com.foo.MyClassType.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -12297,7 +11584,7 @@ in the registry by prefixing with #type: syntax, eg #type:com.foo.MyClassType.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Property key.
+The property key.
]]>
</xs:documentation>
</xs:annotation>
@@ -12315,6 +11602,7 @@ Property key.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -12339,8 +11627,7 @@ Property key.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Delimiter used if the Expression returned multiple endpoints. Can be turned off using the value false. The default value
-is ,. Default value: ,
+Delimiter used if the Expression returned multiple endpoints. Can be turned off using the value false. Default value: ,
]]>
</xs:documentation>
</xs:annotation>
@@ -12349,9 +11636,7 @@ is ,. Default value: ,
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the AggregationStrategy to be used to assemble the replies from the recipients, into a single outgoing message from
-the RecipientList. By default Camel will use the last reply as the outgoing message. You can also use a POJO as the
-AggregationStrategy.
+Sets the AggregationStrategy to be used to assemble the replies from the recipients, into a single outgoing message.
]]>
</xs:documentation>
</xs:annotation>
@@ -12360,7 +11645,7 @@ AggregationStrategy.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-This option can be used to explicit declare the method name to use, when using POJOs as the AggregationStrategy.
+This option can be used to explicitly declare the method name to use, when using POJOs as the AggregationStrategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -12393,14 +11678,7 @@ higher performance when the AggregationStrategy is implemented as thread-safe. D
<xs:documentation xml:lang="en">
<![CDATA[
If enabled then sending messages to the recipients occurs concurrently. Note the caller thread will still wait until all
-messages has been fully processed, before it continues. Its only the sending and processing the replies from the
-recipients which happens concurrently. When parallel processing is enabled, then the Camel routing engin will continue
-processing using last used thread from the parallel thread pool. However, if you want to use the original thread that
-called the recipient list, then make sure to enable the synchronous option as well. In parallel processing mode, you may
-want to also synchronous = true to force this EIP to process the sub-tasks using the upper bounds of the thread-pool. If
-using synchronous = false then Camel will allow its reactive routing engine to use as many threads as possible, which
-may be available due to sub-tasks using other thread-pools such as CompletableFuture.runAsync or others. Default value:
-false
+messages has been fully processed, before it continues. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -12421,9 +11699,7 @@ routing after the recipient list is complete, even if parallel processing is ena
<![CDATA[
Sets a total timeout specified in millis, when using parallel processing. If the Recipient List hasn't been able to send
and process all replies within the given timeframe, then the timeout triggers and the Recipient List breaks out and
-continues. The timeout method is invoked before breaking out. If the timeout is reached with running tasks still
-remaining, certain tasks for which it is difficult for Camel to shut down in a graceful manner may continue to run. So
-use this option with a bit of care. Default value: 0
+continues. Default value: 0
]]>
</xs:documentation>
</xs:annotation>
@@ -12432,8 +11708,8 @@ use this option with a bit of care. Default value: 0
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom Thread Pool to be used for parallel processing. Notice if you set this option, then parallel processing
-is automatic implied, and you do not have to enable that option as well.
+Refers to a custom Thread Pool to be used for parallel processing. Notice if you set this option, then parallel
+processing is automatically implied, and you do not have to enable that option as well.
]]>
</xs:documentation>
</xs:annotation>
@@ -12442,11 +11718,8 @@ is automatic implied, and you do not have to enable that option as well.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will now stop further processing if an exception or failure occurred during processing of an org.apache.camel.Exchange
-and the caused exception will be thrown. Will also stop if processing the exchange failed (has a fault message) or an
-exception was thrown and handled by the error handler (such as using onException). In all situations the recipient list
-will stop further processing. This is the same behavior as in pipeline, which is used by the routing engine. The default
-behavior is to not stop but continue processing till the end. Default value: false
+Stops further processing if an exception or failure occurred during processing of an exchange and the caused exception
+will be thrown. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -12455,7 +11728,7 @@ behavior is to not stop but continue processing till the end. Default value: fal
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Ignore the invalidate endpoint exception when try to create a producer with that endpoint. Default value: false
+Whether to ignore an invalid endpoint URI when trying to create a producer with that endpoint. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -12474,8 +11747,8 @@ replies in the same order as defined by the recipient list. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Uses the Processor when preparing the org.apache.camel.Exchange to be used send. This can be used to deep-clone messages
-that should be send, or any custom logic needed before the exchange is send.
+Uses the Processor when preparing the exchange to be sent. This can be used to deep-clone messages that should be sent,
+or any custom logic needed before the exchange is sent.
]]>
</xs:documentation>
</xs:annotation>
@@ -12484,15 +11757,8 @@ that should be send, or any custom logic needed before the exchange is send.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum size used by the org.apache.camel.spi.ProducerCache which is used to cache and reuse producers when
-using this recipient list, when uris are reused. Beware that when using dynamic endpoints then it affects how well the
-cache can be utilized. If each dynamic endpoint is unique then its best to turn off caching by setting this to -1, which
-allows Camel to not cache both the producers and endpoints; they are regarded as prototype scoped and will be stopped
-and discarded after use. This reduces memory usage as otherwise producers/endpoints are stored in memory in the caches.
-However if there are a high degree of dynamic endpoints that have been used before, then it can benefit to use the cache
-to reuse both producers and endpoints and therefore the cache size can be set accordingly or rely on the default size
-(1000). If there is a mix of unique and used before dynamic endpoints, then setting a reasonable cache size can help
-reduce memory usage to avoid storing too many non frequent used producers.
+Sets the maximum size used by the ProducerCache which is used to cache and reuse producers when uris are reused. Use 0
+for default cache size, or -1 to turn cache off.
]]>
</xs:documentation>
</xs:annotation>
@@ -12501,9 +11767,20 @@ reduce memory usage to avoid storing too many non frequent used producers.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Shares the org.apache.camel.spi.UnitOfWork with the parent and each of the sub messages. Recipient List will by default
-not share unit of work between the parent exchange and each recipient exchange. This means each sub exchange has its own
-individual unit of work. Default value: false
+Shares the UnitOfWork with the parent and each of the sub messages. Recipient List will by default not share unit of
+work between the parent exchange and each recipient exchange. This means each sub exchange has its own individual unit
+of work. Default value: false
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="allowedSchemes" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets an optional comma-separated allow-list of component schemes that the dynamic recipient may resolve to (e.g.
+http,https). When set, a dynamic endpoint whose scheme is not in the list is rejected. This is a defence-in-depth
+restriction, useful for low-code / Kamelet deployments; by default (unset) any scheme is allowed.
]]>
</xs:documentation>
</xs:annotation>
@@ -12535,8 +11812,8 @@ Name of header to remove.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name or pattern of headers to remove. The pattern is matched in the following order: 1 = exact match 2 = wildcard
-(pattern ends with a and the name starts with the pattern) 3 = regular expression (all of above is case in-sensitive).
+Name or pattern of headers to remove. The pattern supports exact match, wildcard (pattern ends with ), and regular
+expression (all case-insensitive).
]]>
</xs:documentation>
</xs:annotation>
@@ -12545,8 +11822,7 @@ Name or pattern of headers to remove. The pattern is matched in the following or
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name or patter of headers to not remove. The pattern is matched in the following order: 1 = exact match 2 = wildcard
-(pattern ends with a and the name starts with the pattern) 3 = regular expression (all of above is case in-sensitive).
+Name or pattern of headers to not remove. You can use comma to separate multiple patterns.
]]>
</xs:documentation>
</xs:annotation>
@@ -12562,8 +11838,8 @@ Name or patter of headers to not remove. The pattern is matched in the following
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name or pattern of properties to remove. The pattern is matched in the following order: 1 = exact match 2 = wildcard
-(pattern ends with a and the name starts with the pattern) 3 = regular expression (all of above is case in-sensitive).
+Name or pattern of properties to remove. Supports exact match, wildcard (ending with ), and regular expression (all
+case-insensitive).
]]>
</xs:documentation>
</xs:annotation>
@@ -12572,8 +11848,7 @@ Name or pattern of properties to remove. The pattern is matched in the following
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name or pattern of properties to not remove. The pattern is matched in the following order: 1 = exact match 2 = wildcard
-(pattern ends with a and the name starts with the pattern) 3 = regular expression (all of above is case in-sensitive).
+Name or pattern of properties to not remove. You can use comma to separate multiple patterns.
]]>
</xs:documentation>
</xs:annotation>
@@ -12589,7 +11864,7 @@ Name or pattern of properties to not remove. The pattern is matched in the follo
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of property to remove.
+Name of the exchange property to remove.
]]>
</xs:documentation>
</xs:annotation>
@@ -12605,7 +11880,7 @@ Name of property to remove.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of variable to remove.
+Name of the variable to remove.
]]>
</xs:documentation>
</xs:annotation>
@@ -12630,6 +11905,7 @@ Name of variable to remove.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -12651,6 +11927,7 @@ Name of variable to remove.
<xs:element ref="tns:xquery"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -12721,7 +11998,6 @@ Name of variable to remove.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -12799,7 +12075,7 @@ Sets the capacity of the resequencer inbound queue. Default value: 1000
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets minimum time (milliseconds) to wait for missing elements (messages). Default value: 1000
+Sets the minimum time (milliseconds) to wait for missing elements (messages). Default value: 1000
]]>
</xs:documentation>
</xs:annotation>
@@ -12808,8 +12084,8 @@ Sets minimum time (milliseconds) to wait for missing elements (messages). Defaul
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the interval in milliseconds the stream resequencer will at most wait while waiting for condition of being able to
-deliver. Default value: 1000
+Sets the interval in milliseconds the stream resequencer will at most wait while waiting for the condition of being able
+to deliver. Default value: 1000
]]>
</xs:documentation>
</xs:annotation>
@@ -12836,7 +12112,7 @@ If true, throws an exception when messages older than the last delivered message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom comparator as a org.apache.camel.processor.resequencer.ExpressionResultComparator type.
+To use a custom comparator for ordering the sequence of messages.
]]>
</xs:documentation>
</xs:annotation>
@@ -12864,7 +12140,7 @@ Reference to the rest-dsl.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the resume strategy to use.
+The resume strategy to use for resuming processing from the last known offset.
]]>
</xs:documentation>
</xs:annotation>
@@ -12882,8 +12158,8 @@ The logging level to use in case of failures. Default value: ERROR
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether the offsets will be intermittently present or whether they must be present in every exchange. Default
-value: false
+Whether the offsets will be intermittently present or whether they must be present in every exchange. Default value:
+false
]]>
</xs:documentation>
</xs:annotation>
@@ -12899,7 +12175,7 @@ value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Message to use in rollback exception.
+The message to set on the exception when rolling back.
]]>
</xs:documentation>
</xs:annotation>
@@ -12908,7 +12184,8 @@ Message to use in rollback exception.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Mark the transaction for rollback only (cannot be overruled to commit). Default value: false
+If enabled then only the current transaction is marked for rollback. No exception is thrown and the route continues to
+execute. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -12917,8 +12194,8 @@ Mark the transaction for rollback only (cannot be overruled to commit). Default
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Mark only last sub transaction for rollback only. When using sub transactions (if the transaction manager support this).
-Default value: false
+If enabled then only the last sub-transaction (from the last transacted EIP) is marked for rollback. This allows partial
+rollbacks in nested transaction scenarios. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -12934,7 +12211,7 @@ Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to the route builder instance.
+Reference to the RouteBuilder instance.
]]>
</xs:documentation>
</xs:annotation>
@@ -12948,7 +12225,7 @@ Reference to the route builder instance.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to the route templates in the xml dsl.
+Reference to the route configuration in the xml-dsl.
]]>
</xs:documentation>
</xs:annotation>
@@ -12969,8 +12246,7 @@ Reference to the route templates in the xml dsl.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The predicate of the precondition in simple language to evaluate in order to determine if this route configuration
-should be included or not.
+Predicate in simple language to evaluate whether this route configuration should be included or not.
]]>
</xs:documentation>
</xs:annotation>
@@ -12993,7 +12269,7 @@ should be included or not.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to the routes in the xml dsl.
+Reference to the routes in the xml-dsl.
]]>
</xs:documentation>
</xs:annotation>
@@ -13009,6 +12285,7 @@ Reference to the routes in the xml dsl.
<xs:element minOccurs="0" ref="tns:inputType"/>
<xs:element minOccurs="0" ref="tns:outputType"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -13079,7 +12356,6 @@ Reference to the routes in the xml dsl.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="autoStartup" type="xs:string">
@@ -13104,7 +12380,8 @@ Whether to slow down processing messages by a given delay in msec. Default value
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the bean ref name of the error handler builder to use on this route.
+Sets a reference to a custom error handler to use for this route, referring to an error handler by its id in the
+registry.
]]>
</xs:documentation>
</xs:annotation>
@@ -13118,12 +12395,11 @@ The group name for this route. Multiple routes can belong to the same group.
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="kamelet" type="xs:boolean"/>
<xs:attribute name="logMask" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether security mask for Logging is enabled on this route. Default value: false
+Whether security mask for logging is enabled on this route. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -13156,7 +12432,6 @@ or not.
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="rest" type="xs:boolean"/>
<xs:attribute name="routeConfigurationId" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
@@ -13171,8 +12446,7 @@ comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to custom org.apache.camel.spi.RoutePolicy to use by the route. Multiple policies can be configured by
-separating values using comma.
+Configures a route policy for this route.
]]>
</xs:documentation>
</xs:annotation>
@@ -13181,7 +12455,8 @@ separating values using comma.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To control how to shutdown the route.
+To control how to shutdown the route. Default shuts down the route normally. Defer delays the shutdown so that in-flight
+and pending messages are allowed to complete before the route is shutdown.
]]>
</xs:documentation>
</xs:annotation>
@@ -13190,7 +12465,9 @@ To control how to shutdown the route.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To control how to shut down the route.
+To control how to handle in-flight and pending messages during shutdown. CompleteCurrentTaskOnly (default) finishes only
+the current message. CompleteAllTasks finishes all pending messages (e.g. from a batch consumer or aggregator) before
+shutting down.
]]>
</xs:documentation>
</xs:annotation>
@@ -13213,7 +12490,6 @@ Whether stream caching is enabled on this route. Default value: false
</xs:documentation>
</xs:annotation>
</xs:attribute>
- <xs:attribute name="template" type="xs:boolean"/>
<xs:attribute name="trace" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
@@ -13232,7 +12508,7 @@ Whether tracing is enabled on this route. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to the route templates in the xml dsl.
+Reference to the route templates in the xml-dsl.
]]>
</xs:documentation>
</xs:annotation>
@@ -13263,7 +12539,7 @@ Adds a local bean the route template uses.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The name of the parameter.
+The name of the template parameter.
]]>
</xs:documentation>
</xs:annotation>
@@ -13272,8 +12548,8 @@ The name of the parameter.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether the parameter is required or not. A parameter is required unless this option is set to false or a default value
-has been configured. Default value: false
+Whether this template parameter is required. A required parameter must have a value provided when creating a route from
+the template. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -13282,7 +12558,8 @@ has been configured. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Default value of the parameter. If a default value is provided then the parameter is implied not to be required.
+The default value of the template parameter. Used when no explicit value is provided when creating a route from the
+template.
]]>
</xs:documentation>
</xs:annotation>
@@ -13291,7 +12568,7 @@ Default value of the parameter. If a default value is provided then the paramete
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Description of the parameter.
+Description of the template parameter for documentation purposes.
]]>
</xs:documentation>
</xs:annotation>
@@ -13327,6 +12604,7 @@ Description of the parameter.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13351,7 +12629,7 @@ Description of the parameter.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the uri delimiter to use. Default value: ,
+The delimiter used to separate endpoint URIs in the routing slip expression. Default is comma. Default value: ,
]]>
</xs:documentation>
</xs:annotation>
@@ -13360,7 +12638,7 @@ Sets the uri delimiter to use. Default value: ,
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Ignore the invalidate endpoint exception when try to create a producer with that endpoint. Default value: false
+If enabled then invalid endpoint URIs are ignored and logged instead of throwing an exception. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -13369,38 +12647,19 @@ Ignore the invalidate endpoint exception when try to create a producer with that
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum size used by the org.apache.camel.spi.ProducerCache which is used to cache and reuse producers when
-using this routing slip, when uris are reused. Beware that when using dynamic endpoints then it affects how well the
-cache can be utilized. If each dynamic endpoint is unique then its best to turn off caching by setting this to -1, which
-allows Camel to not cache both the producers and endpoints; they are regarded as prototype scoped and will be stopped
-and discarded after use. This reduces memory usage as otherwise producers/endpoints are stored in memory in the caches.
-However if there are a high degree of dynamic endpoints that have been used before, then it can benefit to use the cache
-to reuse both producers and endpoints and therefore the cache size can be set accordingly or rely on the default size
-(1000). If there is a mix of unique and used before dynamic endpoints, then setting a reasonable cache size can help
-reduce memory usage to avoid storing too many non frequent used producers.
+Configures the cache size for ProducerCache which caches producers for reuse. The default cache size is 1000. Set to -1
+to turn off caching.
]]>
</xs:documentation>
</xs:annotation>
</xs:attribute>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType name="sagaActionUriDefinition">
- <xs:complexContent>
- <xs:extension base="tns:sendDefinition">
- <xs:sequence/>
- </xs:extension>
- </xs:complexContent>
- </xs:complexType>
- <xs:complexType abstract="true" name="sendDefinition">
- <xs:complexContent>
- <xs:extension base="tns:noOutputDefinition">
- <xs:sequence/>
- <xs:attribute name="uri" type="xs:string">
+ <xs:attribute name="allowedSchemes" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the uri of the endpoint to send to.
+Sets an optional comma-separated allow-list of component schemes that the dynamic recipient may resolve to (e.g.
+http,https). When set, a dynamic endpoint whose scheme is not in the list is rejected. This is a defence-in-depth
+restriction, useful for low-code / Kamelet deployments; by default (unset) any scheme is allowed.
]]>
</xs:documentation>
</xs:annotation>
@@ -13412,40 +12671,18 @@ Sets the uri of the endpoint to send to.
<xs:complexContent>
<xs:extension base="tns:output">
<xs:sequence>
- <xs:element minOccurs="0" name="compensation" type="tns:sagaActionUriDefinition">
+ <xs:element maxOccurs="unbounded" minOccurs="0" name="option" type="tns:propertyExpressionDefinition">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The compensation endpoint URI that must be called to compensate all changes done in the route. The route corresponding
-to the compensation URI must perform compensation and complete without error. If errors occur during compensation, the
-saga service may call again the compensation URI to retry.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element minOccurs="0" name="completion" type="tns:sagaActionUriDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-The completion endpoint URI that will be called when the Saga is completed successfully. The route corresponding to the
-completion URI must perform completion tasks and terminate without error. If errors occur during completion, the saga
-service may call again the completion URI to retry.
-]]>
- </xs:documentation>
- </xs:annotation>
- </xs:element>
- <xs:element maxOccurs="unbounded" minOccurs="0" name="option" type="tns:propertyExpressionDefinition">
- <xs:annotation>
- <xs:documentation xml:lang="en">
-<![CDATA[
-Allows to save properties of the current exchange in order to re-use them in a compensation/completion callback route.
-Options are usually helpful e.g. to store and retrieve identifiers of objects that should be deleted in compensating
-actions. Option values will be transformed into input headers of the compensation/completion exchange.
+Allows to save properties of the current exchange in order to re-use them in a compensation/completion callback route.
+Option values will be transformed into input headers of the compensation/completion exchange.
]]>
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -13516,7 +12753,6 @@ actions. Option values will be transformed into input headers of the compensatio
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="sagaService" type="xs:string">
@@ -13532,8 +12768,10 @@ Refers to the id to lookup in the registry for the specific CamelSagaService to
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Set the Saga propagation mode (REQUIRED, REQUIRES_NEW, MANDATORY, SUPPORTS, NOT_SUPPORTED, NEVER). Default value:
-REQUIRED
+Set the Saga propagation mode. REQUIRED joins an existing saga or starts a new one. REQUIRES_NEW always starts a new
+saga, suspending any existing one. MANDATORY requires an existing saga and fails if none is active. SUPPORTS joins an
+existing saga if present but does not start a new one. NOT_SUPPORTED executes outside any saga, suspending an existing
+one. NEVER fails if a saga is already active. Default value: REQUIRED
]]>
</xs:documentation>
</xs:annotation>
@@ -13542,9 +12780,9 @@ REQUIRED
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Determine how the saga should be considered complete. When set to AUTO, the saga is completed when the exchange that
-initiates the saga is processed successfully, or compensated when it completes exceptionally. When set to MANUAL, the
-user must complete or compensate the saga using the saga:complete or saga:compensate endpoints. Default value: AUTO
+Determine how the saga should be considered complete. When set to AUTO, the saga is completed when the exchange is
+processed successfully, or compensated when it completes exceptionally. When set to MANUAL, the user must complete or
+compensate the saga using the saga:complete or saga:compensate endpoints. Default value: AUTO
]]>
</xs:documentation>
</xs:annotation>
@@ -13555,6 +12793,26 @@ user must complete or compensate the saga using the saga:complete or saga:compen
<![CDATA[
Set the maximum amount of time for the Saga. After the timeout is expired, the saga will be compensated automatically
(unless a different decision has been taken in the meantime).
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="compensation" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The compensation endpoint URI that must be called to compensate all changes done in the route. The route corresponding
+to the compensation URI must perform compensation and complete without error.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="completion" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The completion endpoint URI that will be called when the Saga is completed successfully. The route corresponding to the
+completion URI must perform completion tasks and terminate without error.
]]>
</xs:documentation>
</xs:annotation>
@@ -13570,7 +12828,7 @@ Set the maximum amount of time for the Saga. After the timeout is expired, the s
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the sample period during which only a single Exchange will pass through. Default value: 1000
+The period between samples, using a time-based approach. Default is 1 second. Default value: 1000
]]>
</xs:documentation>
</xs:annotation>
@@ -13579,7 +12837,8 @@ Sets the sample period during which only a single Exchange will pass through. De
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the sample message count which only a single Exchange will pass through after this many received.
+The frequency of samples as a message count, using a message-frequency approach. For example, a value of 5 means every
+5th message is sampled.
]]>
</xs:documentation>
</xs:annotation>
@@ -13599,6 +12858,7 @@ Sets the sample message count which only a single Exchange will pass through aft
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13622,6 +12882,22 @@ Sets the sample message count which only a single Exchange will pass through aft
</xs:extension>
</xs:complexContent>
</xs:complexType>
+ <xs:complexType abstract="true" name="sendDefinition">
+ <xs:complexContent>
+ <xs:extension base="tns:noOutputDefinition">
+ <xs:sequence/>
+ <xs:attribute name="uri" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+The uri of the endpoint to send to.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ </xs:extension>
+ </xs:complexContent>
+ </xs:complexType>
<xs:complexType name="setBodyDefinition">
<xs:complexContent>
<xs:extension base="tns:processorDefinition">
@@ -13634,6 +12910,7 @@ Sets the sample message count which only a single Exchange will pass through aft
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13665,7 +12942,7 @@ Sets the sample message count which only a single Exchange will pass through aft
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the new exchange pattern of the Exchange to be used from this point forward.
+The new exchange pattern to use from this point forward.
]]>
</xs:documentation>
</xs:annotation>
@@ -13685,6 +12962,7 @@ Sets the new exchange pattern of the Exchange to be used from this point forward
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13709,8 +12987,8 @@ Sets the new exchange pattern of the Exchange to be used from this point forward
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of message header to set a new value The simple language can be used to define a dynamic evaluated header name to
-be used. Otherwise a constant name will be used.
+Name of message header to set a new value. The simple language can be used to define a dynamic evaluated header name.
+Otherwise a constant name will be used.
]]>
</xs:documentation>
</xs:annotation>
@@ -13739,6 +13017,7 @@ be used. Otherwise a constant name will be used.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13763,8 +13042,8 @@ be used. Otherwise a constant name will be used.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of exchange property to set a new value. The simple language can be used to define a dynamic evaluated exchange
-property name to be used. Otherwise a constant name will be used.
+Name of exchange property to set a new value. The simple language can be used to define a dynamic evaluated property
+name. Otherwise a constant name will be used.
]]>
</xs:documentation>
</xs:annotation>
@@ -13784,6 +13063,7 @@ property name to be used. Otherwise a constant name will be used.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13808,8 +13088,8 @@ property name to be used. Otherwise a constant name will be used.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Name of variable to set a new value The simple language can be used to define a dynamic evaluated variable name to be
-used. Otherwise a constant name will be used.
+Name of variable to set a new value. The simple language can be used to define a dynamic evaluated variable name.
+Otherwise a constant name will be used.
]]>
</xs:documentation>
</xs:annotation>
@@ -13838,6 +13118,7 @@ used. Otherwise a constant name will be used.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13862,7 +13143,7 @@ used. Otherwise a constant name will be used.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the comparator to use for sorting.
+Sets a reference to lookup for the comparator to use for sorting.
]]>
</xs:documentation>
</xs:annotation>
@@ -13883,6 +13164,7 @@ Sets the comparator to use for sorting.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -13904,6 +13186,7 @@ Sets the comparator to use for sorting.
<xs:element ref="tns:xquery"/>
</xs:choice>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -13974,7 +13257,6 @@ Sets the comparator to use for sorting.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="delimiter" type="xs:string">
@@ -13982,8 +13264,7 @@ Sets the comparator to use for sorting.
<xs:documentation xml:lang="en">
<![CDATA[
Delimiter used in splitting messages. Can be turned off using the value false. To force not splitting then the delimiter
-can be set to single to use the value as a single list, this can be needed in some special situations. The default value
-is comma. Default value: ,
+can be set to single to use the value as a single list. The default value is comma. Default value: ,
]]>
</xs:documentation>
</xs:annotation>
@@ -13992,9 +13273,8 @@ is comma. Default value: ,
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to the AggregationStrategy to be used to assemble the replies from the split messages, into a single
-outgoing message from the Splitter. By default Camel will use the original incoming message to the splitter (leave it
-unchanged). You can also use a POJO as the AggregationStrategy.
+Reference to the AggregationStrategy to assemble the replies from the split messages into a single outgoing message. By
+default Camel uses the original incoming message.
]]>
</xs:documentation>
</xs:annotation>
@@ -14003,7 +13283,7 @@ unchanged). You can also use a POJO as the AggregationStrategy.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-This option can be used to explicit declare the method name to use, when using POJOs as the AggregationStrategy.
+The method name to use when using a POJO as the AggregationStrategy.
]]>
</xs:documentation>
</xs:annotation>
@@ -14012,9 +13292,8 @@ This option can be used to explicit declare the method name to use, when using P
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If this option is false then the aggregate method is not used if there was no data to enrich. If this option is true
-then null values is used as the oldExchange (when no data to enrich), when using POJOs as the AggregationStrategy.
-Default value: false
+If true then null is used as the oldExchange when there is no data to aggregate, when using POJOs as the
+AggregationStrategy. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14035,14 +13314,8 @@ higher performance when the AggregationStrategy is implemented as thread-safe. D
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-If enabled then processing each split messages occurs concurrently. Note the caller thread will still wait until all
-messages has been fully processed, before it continues. It's only processing the sub messages from the splitter which
-happens concurrently. When parallel processing is enabled, then the Camel routing engin will continue processing using
-last used thread from the parallel thread pool. However, if you want to use the original thread that called the
-splitter, then make sure to enable the synchronous option as well. In parallel processing mode, you may want to also
-synchronous = true to force this EIP to process the sub-tasks using the upper bounds of the thread-pool. If using
-synchronous = false then Camel will allow its reactive routing engine to use as many threads as possible, which may be
-available due to sub-tasks using other thread-pools such as CompletableFuture.runAsync or others. Default value: false
+If enabled then processing each split message occurs concurrently. The caller thread still waits until all messages are
+fully processed before it continues. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14051,8 +13324,8 @@ available due to sub-tasks using other thread-pools such as CompletableFuture.ru
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets whether synchronous processing should be strictly used. When enabled then the same thread is used to continue
-routing after the split is complete, even if parallel processing is enabled. Default value: false
+When enabled then the same thread is used to continue routing after the split is complete, even if parallel processing
+is enabled. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14061,14 +13334,8 @@ routing after the split is complete, even if parallel processing is enabled. Def
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-When in streaming mode, then the splitter splits the original message on-demand, and each split message is processed one
-by one. This reduces memory usage as the splitter do not split all the messages first, but then we do not know the total
-size, and therefore the org.apache.camel.Exchange#SPLIT_SIZE is empty. In non-streaming mode (default) the splitter will
-split each message first, to know the total size, and then process each message one by one. This requires to keep all
-the split messages in memory and therefore requires more memory. The total size is provided in the
-org.apache.camel.Exchange#SPLIT_SIZE header. The streaming mode also affects the aggregation behavior. If enabled then
-Camel will process replies out-of-order, e.g. in the order they come back. If disabled, Camel will process replies in
-the same order as the messages was split. Default value: false
+When enabled then the splitter splits the original message on-demand, and each split message is processed one by one.
+This reduces memory usage as the splitter does not split all messages first. Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14077,11 +13344,9 @@ the same order as the messages was split. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Will now stop further processing if an exception or failure occurred during processing of an org.apache.camel.Exchange
-and the caused exception will be thrown. Will also stop if processing the exchange failed (has a fault message) or an
-exception was thrown and handled by the error handler (such as using onException). In all situations the splitter will
-stop further processing. This is the same behavior as in pipeline, which is used by the routing engine. The default
-behavior is to not stop but continue processing till the end. Default value: false
+If enabled then stops further split processing if an exception or failure occurred during processing of a split message,
+and the caused exception will be thrown. The default behavior is to not stop but continue processing till the end.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14090,11 +13355,8 @@ behavior is to not stop but continue processing till the end. Default value: fal
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a total timeout specified in millis, when using parallel processing. If the Splitter hasn't been able to send and
-process all replies within the given timeframe, then the timeout triggers and the Splitter breaks out and continues. The
-timeout method is invoked before breaking out. If the timeout is reached with running tasks still remaining, certain
-tasks for which it is difficult for Camel to shut down in a graceful manner may continue to run. So use this option with
-a bit of care. Default value: 0
+Total timeout in millis when using parallel processing. If the splitter has not been able to process all replies within
+the given timeframe, then the timeout triggers and the splitter breaks out and continues. Default value: 0
]]>
</xs:documentation>
</xs:annotation>
@@ -14103,8 +13365,7 @@ a bit of care. Default value: 0
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom Thread Pool to be used for parallel processing. Notice if you set this option, then parallel processing
-is automatically implied, and you do not have to enable that option as well.
+Reference to a custom thread pool to use for parallel processing. Setting this option implies parallel processing.
]]>
</xs:documentation>
</xs:annotation>
@@ -14113,8 +13374,7 @@ is automatically implied, and you do not have to enable that option as well.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Uses the Processor when preparing the org.apache.camel.Exchange to be sent. This can be used to deep-clone messages that
-should be sent, or any custom logic needed before the exchange is sent.
+Reference to a processor for preparing the exchange to be sent. Can be used to deep-clone messages that should be sent.
]]>
</xs:documentation>
</xs:annotation>
@@ -14123,9 +13383,72 @@ should be sent, or any custom logic needed before the exchange is sent.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Shares the org.apache.camel.spi.UnitOfWork with the parent and each of the sub messages. Splitter will by default not
-share unit of work between the parent exchange and each split exchange. This means each split exchange has its own
+Shares the unit of work with the parent and each of the split messages. By default each split exchange has its own
individual unit of work. Default value: false
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="group" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Groups N split messages into a single message with a java.util.List body. This allows processing items in chunks instead
+of one at a time.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="errorThreshold" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets the error threshold as a fraction (0.0-1.0) of failed items before aborting the split operation. For example, 0.1
+means abort if more than 10% of items fail. When the threshold is exceeded, a org.apache.camel.CamelExchangeException is
+thrown. This option is mutually exclusive with stopOnException . When set, individual item failures are tracked but
+processing continues until the threshold is exceeded. Note: When combined with parallelProcessing , the failure ratio
+may vary between runs because parallel items complete in non-deterministic order. For deterministic abort behavior with
+parallel processing, prefer maxFailedRecords (absolute count) over errorThreshold (ratio).
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="maxFailedRecords" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets the maximum number of failed records before aborting the split operation. When the count is exceeded, a
+org.apache.camel.CamelExchangeException is thrown. This option is mutually exclusive with stopOnException . Can be
+combined with errorThreshold processing aborts when either threshold is exceeded.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="resumeStrategy" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets a ResumeStrategy for resume-from-last-position support. The watermark key must also be configured via
+watermarkKey(String) .
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="watermarkKey" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets the key to use in the watermark store.
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="watermarkExpression" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets a Simple expression to evaluate on each completed sub-exchange to determine the new watermark value. When set,
+enables value-based watermarking instead of index-based. The expression is evaluated using the Simple language.
]]>
</xs:documentation>
</xs:annotation>
@@ -14138,6 +13461,7 @@ individual unit of work. Default value: false
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -14208,7 +13532,6 @@ individual unit of work. Default value: false
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -14246,7 +13569,7 @@ Adds a local bean as input of the template to build the route.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the id of the route template to use to build the route.
+The id of the route template to use to build the route.
]]>
</xs:documentation>
</xs:annotation>
@@ -14255,7 +13578,7 @@ Sets the id of the route template to use to build the route.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the id of the route built from the route template.
+The id of the route built from the route template.
]]>
</xs:documentation>
</xs:annotation>
@@ -14326,7 +13649,7 @@ Whether this profile is the default thread pool profile. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the core pool size.
+Sets the core pool size (number of threads to keep in the pool, even if idle).
]]>
</xs:documentation>
</xs:annotation>
@@ -14335,7 +13658,7 @@ Sets the core pool size.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum pool size.
+Sets the maximum pool size (the upper bound of threads in the pool).
]]>
</xs:documentation>
</xs:annotation>
@@ -14344,7 +13667,7 @@ Sets the maximum pool size.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the keep alive time for idle threads in the pool.
+Sets the keep alive time for idle threads before they are terminated. Only applies to threads above the core pool size.
]]>
</xs:documentation>
</xs:annotation>
@@ -14353,7 +13676,7 @@ Sets the keep alive time for idle threads in the pool.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the time unit to use for keep alive time By default SECONDS is used.
+Sets the time unit to use for keep alive time. By default SECONDS is used.
]]>
</xs:documentation>
</xs:annotation>
@@ -14371,8 +13694,8 @@ Sets the maximum number of tasks in the work queue. Use -1 or Integer.MAX_VALUE
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether idle core threads is allowed to timeout and therefore can shrink the pool size below the core pool size Is by
-default true. Default value: false
+Whether idle core threads are allowed to timeout and therefore can shrink the pool size below the core pool size.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14397,7 +13720,7 @@ Sets the handler for tasks which cannot be executed by the thread pool.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a custom thread pool.
+To refer to a custom thread pool or use a thread pool profile (as overlay).
]]>
</xs:documentation>
</xs:annotation>
@@ -14406,7 +13729,7 @@ To use a custom thread pool.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the core pool size.
+Sets the core pool size (number of threads to keep in the pool, even if idle).
]]>
</xs:documentation>
</xs:annotation>
@@ -14415,7 +13738,7 @@ Sets the core pool size.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum pool size.
+Sets the maximum pool size (the upper bound of threads in the pool).
]]>
</xs:documentation>
</xs:annotation>
@@ -14424,7 +13747,7 @@ Sets the maximum pool size.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the keep alive time for idle threads.
+Sets the keep alive time for idle threads before they are terminated. Only applies to threads above the core pool size.
]]>
</xs:documentation>
</xs:annotation>
@@ -14433,7 +13756,7 @@ Sets the keep alive time for idle threads.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the keep alive time unit. By default SECONDS is used.
+Sets the time unit for the keep alive time. By default SECONDS is used.
]]>
</xs:documentation>
</xs:annotation>
@@ -14451,8 +13774,8 @@ Sets the maximum number of tasks in the work queue. Use -1 or Integer.MAX_VALUE
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether idle core threads are allowed to timeout and therefore can shrink the pool size below the core pool size Is by
-default false. Default value: false
+Whether idle core threads are allowed to timeout and therefore can shrink the pool size below the core pool size.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14461,7 +13784,7 @@ default false. Default value: false
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the thread name to use. Default value: Threads
+Sets the thread name pattern to use for naming threads created by this thread pool. Default value: Threads
]]>
</xs:documentation>
</xs:annotation>
@@ -14479,9 +13802,9 @@ Sets the handler for tasks which cannot be executed by the thread pool.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not to use as caller runs as fallback when a task is rejected being added to the thread pool (when its full).
+Whether to use the caller thread as fallback when a task is rejected being added to the thread pool (when its full).
This is only used as fallback if no rejectedPolicy has been configured, or the thread pool has no configured rejection
-handler. Is by default true. Default value: true
+handler. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -14502,6 +13825,7 @@ handler. Is by default true. Default value: true
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -14526,8 +13850,7 @@ handler. Is by default true. Default value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The expression used to calculate the correlation key to use for throttle grouping. The Exchange which has the same
-correlation key is throttled together.
+The correlation expression to use for throttle grouping. Exchanges with the same correlation key are throttled together.
]]>
</xs:documentation>
</xs:annotation>
@@ -14537,7 +13860,9 @@ correlation key is throttled together.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the throttling mode to one of the available modes enumerated in ThrottlingMode. Default value: TotalRequests
+Sets the throttling mode. TotalRequests limits the total number of requests within a time period. ConcurrentRequests
+uses a leaky-bucket algorithm to limit the number of concurrent requests being processed at the same time. Default
+value: TotalRequests
]]>
</xs:documentation>
</xs:annotation>
@@ -14564,8 +13889,7 @@ Enables asynchronous delay which means the thread will not block while delaying.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not the caller should run the task when it was rejected by the thread pool. Is by default true. Default
-value: true
+Whether or not the caller should run the task when it was rejected by the thread pool. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -14574,8 +13898,8 @@ value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether or not throttler throws the ThrottlerRejectedExecutionException when the exchange exceeds the request limit Is
-by default false. Default value: false
+Whether or not throttler throws the ThrottlerRejectedExecutionException when the exchange exceeds the request limit.
+Default value: false
]]>
</xs:documentation>
</xs:annotation>
@@ -14600,7 +13924,7 @@ Sets the time period during which the maximum request count is valid for. Defaul
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To create a new exception instance and use the given message as caused message (supports simple language).
+The message text for the exception to be thrown. Supports simple language expressions.
]]>
</xs:documentation>
</xs:annotation>
@@ -14609,7 +13933,7 @@ To create a new exception instance and use the given message as caused message (
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The class of the exception to create using the message.
+The fully qualified class name of the exception to throw. Used together with message.
]]>
</xs:documentation>
</xs:annotation>
@@ -14618,7 +13942,7 @@ The class of the exception to create using the message.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Reference to the exception instance to lookup from the registry to throw.
+Reference to an existing exception instance to lookup from the registry and throw.
]]>
</xs:documentation>
</xs:annotation>
@@ -14635,9 +13959,7 @@ Reference to the exception instance to lookup from the registry to throw.
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to
-easily control what data to use for sending and receiving. Important: When using send variable then the message body is
-taken from this variable instead of the current message, however the headers from the message will still be used as
-well. In other words, the variable is used instead of the message body, but everything else is as usual.
+easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -14647,8 +13969,7 @@ well. In other words, the variable is used instead of the message body, but ever
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
-user data and to easily control what data to use for sending and receiving. Important: When using receive variable then
-the received body is stored only in this variable and not on the current message.
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -14657,7 +13978,7 @@ the received body is stored only in this variable and not on the current message
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the optional ExchangePattern used to invoke this endpoint.
+Sets the optional ExchangePattern to use. If not specified the default exchange pattern is used.
]]>
</xs:documentation>
</xs:annotation>
@@ -14673,8 +13994,7 @@ Sets the optional ExchangePattern used to invoke this endpoint.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The uri of the endpoint to send to. The uri can be dynamic computed using the
-org.apache.camel.language.simple.SimpleLanguage expression.
+The uri of the endpoint to send to. The uri can be dynamic computed using the simple language.
]]>
</xs:documentation>
</xs:annotation>
@@ -14684,9 +14004,7 @@ org.apache.camel.language.simple.SimpleLanguage expression.
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to
-easily control what data to use for sending and receiving. Important: When using send variable then the message body is
-taken from this variable instead of the current message, however the headers from the message will still be used as
-well. In other words, the variable is used instead of the message body, but everything else is as usual.
+easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -14695,10 +14013,8 @@ well. In other words, the variable is used instead of the message body, but ever
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to
-easily control what data to use for sending and receiving. Important: When using send variable then the message body is
-taken from this variable instead of the current Message , however the headers from the Message will still be used as
-well. In other words, the variable is used instead of the message body, but everything else is as usual.
+To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -14716,15 +14032,8 @@ Sets the optional ExchangePattern used to invoke this endpoint.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum size used by the org.apache.camel.spi.ProducerCache which is used to cache and reuse producers when
-using this recipient list, when uris are reused. Beware that when using dynamic endpoints then it affects how well the
-cache can be utilized. If each dynamic endpoint is unique then its best to turn off caching by setting this to -1, which
-allows Camel to not cache both the producers and endpoints; they are regarded as prototype scoped and will be stopped
-and discarded after use. This reduces memory usage as otherwise producers/endpoints are stored in memory in the caches.
-However if there are a high degree of dynamic endpoints that have been used before, then it can benefit to use the cache
-to reuse both producers and endpoints and therefore the cache size can be set accordingly or rely on the default size
-(1000). If there is a mix of unique and used before dynamic endpoints, then setting a reasonable cache size can help
-reduce memory usage to avoid storing too many non frequent used producers.
+Sets the maximum size used by the ProducerCache which is used to cache and reuse producers when uris are reused. Use 0
+for default cache size, or -1 to turn cache off.
]]>
</xs:documentation>
</xs:annotation>
@@ -14742,7 +14051,7 @@ Whether to ignore invalid endpoint URIs and skip sending the message. Default va
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Whether to allow components to optimise toD if they are org.apache.camel.spi.SendDynamicAware . Default value: true
+Whether to allow components to optimise toD if they are SendDynamicAware. Default value: true
]]>
</xs:documentation>
</xs:annotation>
@@ -14752,6 +14061,17 @@ Whether to allow components to optimise toD if they are org.apache.camel.spi.Sen
<xs:documentation xml:lang="en">
<![CDATA[
Whether to auto startup components when toD is starting up. Default value: true
+]]>
+ </xs:documentation>
+ </xs:annotation>
+ </xs:attribute>
+ <xs:attribute name="allowedSchemes" type="xs:string">
+ <xs:annotation>
+ <xs:documentation xml:lang="en">
+<![CDATA[
+Sets an optional comma-separated allow-list of component schemes that the dynamic recipient may resolve to (e.g.
+http,https). When set, a dynamic endpoint whose scheme is not in the list is rejected. This is a defence-in-depth
+restriction, useful for low-code / Kamelet deployments; by default (unset) any scheme is allowed.
]]>
</xs:documentation>
</xs:annotation>
@@ -14789,7 +14109,7 @@ Whether to auto startup components when toD is starting up. Default value: true
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the tokenizer type.
+The tokenizer type. Must be one of OPEN_AI, AZURE or QWEN.
]]>
</xs:documentation>
</xs:annotation>
@@ -14798,7 +14118,7 @@ Sets the tokenizer type.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum number of tokens on each segment.
+The maximum number of tokens on each segment.
]]>
</xs:documentation>
</xs:annotation>
@@ -14807,7 +14127,7 @@ Sets the maximum number of tokens on each segment.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the maximum number of tokens that can overlap in each segment.
+The maximum number of tokens that can overlap in each segment.
]]>
</xs:documentation>
</xs:annotation>
@@ -14816,7 +14136,7 @@ Sets the maximum number of tokens that can overlap in each segment.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets the model name.
+The underlying model name used by the tokenizer. Providing this switches to computing segment sizes in terms of tokens.
]]>
</xs:documentation>
</xs:annotation>
@@ -14864,6 +14184,7 @@ Sets the model name.
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -14934,14 +14255,13 @@ Sets the model name.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="ref" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-Sets a reference to use for lookup the policy in the registry.
+Reference to lookup a transacted policy in the registry.
]]>
</xs:documentation>
</xs:annotation>
@@ -14957,7 +14277,8 @@ Sets a reference to use for lookup the policy in the registry.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-From type used in data type transformation.
+The source data type URN in the format 'scheme:name' (e.g. 'java:com.example.MyClass'). If not specified, the current
+message body type is used.
]]>
</xs:documentation>
</xs:annotation>
@@ -14966,7 +14287,8 @@ From type used in data type transformation.
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-To type used as a target data type in the transformation.
+The target data type URN in the format 'scheme:name' (e.g. 'json:JsonOrder') that the message body should be transformed
+into.
]]>
</xs:documentation>
</xs:annotation>
@@ -14986,6 +14308,7 @@ To type used as a target data type in the transformation.
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -15014,6 +14337,7 @@ To type used as a target data type in the transformation.
<xs:extension base="tns:output">
<xs:sequence>
<xs:choice maxOccurs="unbounded" minOccurs="0">
+ <xs:element ref="tns:a2aSubTask"/>
<xs:element ref="tns:aggregate"/>
<xs:element ref="tns:bean"/>
<xs:element ref="tns:doCatch"/>
@@ -15084,7 +14408,6 @@ To type used as a target data type in the transformation.
<xs:element ref="tns:unmarshal"/>
<xs:element ref="tns:validate"/>
<xs:element ref="tns:wireTap"/>
- <xs:element ref="tns:serviceCall"/>
</xs:choice>
</xs:sequence>
</xs:extension>
@@ -15111,6 +14434,7 @@ To type used as a target data type in the transformation.
<xs:element ref="tns:flatpack"/>
<xs:element ref="tns:fory"/>
<xs:element ref="tns:grok"/>
+ <xs:element ref="tns:groovyJson"/>
<xs:element ref="tns:groovyXml"/>
<xs:element ref="tns:gzipDeflater"/>
<xs:element ref="tns:hl7"/>
@@ -15124,6 +14448,8 @@ To type used as a target data type in the transformation.
<xs:element ref="tns:mimeMultipart"/>
<xs:element ref="tns:ocsf"/>
<xs:element ref="tns:parquetAvro"/>
+ <xs:element ref="tns:pgp"/>
+ <xs:element ref="tns:pqc"/>
<xs:element ref="tns:protobuf"/>
<xs:element ref="tns:rss"/>
<xs:element ref="tns:smooks"/>
@@ -15137,8 +14463,6 @@ To type used as a target data type in the transformation.
<xs:element ref="tns:univocityFixed"/>
<xs:element ref="tns:univocityTsv"/>
<xs:element ref="tns:xmlSecurity"/>
- <xs:element ref="tns:pgp"/>
- <xs:element ref="tns:pqc"/>
<xs:element ref="tns:yaml"/>
<xs:element ref="tns:zipDeflater"/>
<xs:element ref="tns:zipFile"/>
@@ -15149,9 +14473,7 @@ To type used as a target data type in the transformation.
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable as the source for the message body to send. This makes it handy to use variables for user data and to
-easily control what data to use for sending and receiving. Important: When using send variable then the message body is
-taken from this variable instead of the current message, however the headers from the message will still be used as
-well. In other words, the variable is used instead of the message body, but everything else is as usual.
+easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -15161,8 +14483,7 @@ well. In other words, the variable is used instead of the message body, but ever
<xs:documentation xml:lang="en">
<![CDATA[
To use a variable to store the received message body (only body, not headers). This makes it handy to use variables for
-user data and to easily control what data to use for sending and receiving. Important: When using receive variable then
-the received body is stored only in this variable and not on the current message.
+user data and to easily control what data to use for sending and receiving.
]]>
</xs:documentation>
</xs:annotation>
@@ -15191,6 +14512,7 @@ Indicates whether null is allowed as value of a body to unmarshall. Default valu
<xs:element ref="tns:groovy"/>
<xs:element ref="tns:header"/>
<xs:element ref="tns:hl7terser"/>
+ <xs:element ref="tns:jactl"/>
<xs:element ref="tns:java"/>
<xs:element ref="tns:js"/>
<xs:element ref="tns:joor"/>
@@ -15215,9 +14537,7 @@ Indicates whether null is allowed as value of a body to unmarshall. Default valu
<xs:annotation>
<xs:documentation xml:lang="en">
<![CDATA[
-The bean id of custom PredicateExceptionFactory to use for creating the exception when the validation fails. By default,
-Camel will throw PredicateValidationException. By using a custom factory you can control which exception to throw
-instead.
+Reference to a custom PredicateExceptionFactory for creating the exception when validation fails.
]]>
</xs:documentation>
</xs:annotation>
@@ -15236,7 +14556,7 @@ instead.
... 4059 lines suppressed ...