Skip to main content Skip to complementary content

cSplitter Standard properties

These properties are used to configure cSplitter running in the Standard Job framework.

The Standard cSplitter component belongs to the Routing family.

Basic settings

Language

Select the language of the expression you want to use to split your messages, from None, Constant, EL, Groovy, Header, JoSQL, JSonPath, JXPath, MVEL, OGNL, PHP, Property, Python, Ruby, Simple, SpEL, SQL, XPath, and XQuery.

For more information about how to use the languages to create an expression, see the site http://camel.apache.org/languages.html.

Correlation expression/Expression

Type in the expression to use to split the messages.

Correlation expression/Use Result Class Type

This option appears when XPath is selected in the Language list.

Select this check box to set the result type of the sub-messages in the field that appears. The default native XML objects org.w3c.dom.NodeList will be used if not specified.

Correlation expression/Add Namespaces

This option appears when XPath is selected in the Language list.

Select this check box to add namespaces for the Xpath expression. Click [+] to add as many namespaces as required to the table and define the prefix and URI in the corresponding columns.

Use Strategy Select this check box to refer to an aggregation strategy to assemble the replies from the sub-messages into a single outgoing message from the splitter. Enter the ID of the aggregation strategy or select a predefined aggregation strategy.
  • UseOriginalAggregationStrategy: Use the original exchange.
  • UseLatestAggregationStrategy: Use the latest exchange.
  • GroupedMessageAggregationStrategy: Aggregate all messages into a single combined exchange holding all the aggregated messages in a list of messages as the message body.
  • GroupedExchangeAggregationStrategy: Aggregate all exchanges into a single combined exchange holding all the aggregated exchanges in a list of exchanges as the message body.
  • GroupedBodyAggregationStrategy: Aggregate body of input messages into a single combined exchange holding all the aggregated bodies in a list of type objects as the message body.
Information noteNote: The predefined aggregation strategies are available only if you have installed the R2024-10 Talend Studio Monthly update or a later one delivered by Talend. For more information, check with your administrator.

The sub-message replies will be aggregated in the order they come back if Streaming is enabled. If not, the sub-message replies will be aggregated in the same order as they were split.

Parameters/Parallel Processing Select this check box to process the sub-messages concurrently. The caller thread will wait until all sub-messages have been fully processed before it continues.
Parameters/Stop on Exception Select this check box to stop processing immediately when an exception occurs.
Parameters/Streaming Select this check box to split the message in a streaming fashion, which means it will split the input message in chunks. It is recommended to enable this option when processing big messages.
Parameters/Share Unit of Work Select this check box to share the unit of work between the parent exchange and each split exchange. For more information and an use case of this option, see the site http://camel.apache.org/splitter.html.
Parameters/Timeout Specify a total timeout in millisecond. If the message is not split and processed within the given time frame, the timeout triggers and the splitter breaks out.

If you have installed the R2023-05 Talend Studio Monthly update or a later one delivered by Talend, you can use context variables of String or Long type in the Timeout parameter.

Usage

Usage rule

cSplitter is used as a middle component in a Route.

Connections split: Select this link to route the split messages to the next endpoint.
Route: Select this link to route all the messages from the sender to the next endpoint.

Limitation

 n/a

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!