Skip to main content Skip to complementary content

cRecipientList Standard properties

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

The Standard cRecipientList component belongs to the Routing family.

Basic settings

Language

Select the expression language from None, Bean, Constant, CorrelationID, 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.

Expression

Type in the expression that returns multiple endpoints.

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.
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 Delimiter Select this check box to customize the separator for the Expression. Enter the characters, strings or regular expressions to be used as the separator in the Delimiter field.
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 recipient list. Enter the ID of the aggregation strategy in the field 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.

Parallel Processing

Select this check box to send the message to the recipients simultaneously.

Use ExecutorService This option appears when Parallel Processing is enabled. Select this check box to use a custom thread pool for parallel processing. Specify the thread pool in the ExecutorService field.

Stop On Exception

Select this check box to stop processing immediately when an exception occurred.

Ignore Invalid Endpoints

Select this check box to ignore invalid endpoints.

Streaming Select this check box to process the sub-message replies in the order that the replies are received from each recipient. If this option is disabled, the replies will be processed in the same order as specified by the Expression.
Timeout Specify a total timeout in millisecond. If the message is not routed to the recipients and processed within the given time frame, the timeout triggers and the recipient list breaks out.
Use On-Prepare Processor Select this check box to use a custom processor to prepare the copy of the exchange that each recipient will receive. Enter the ID of the processor in the next field. You can use the cBeanRegister to register a Java bean as a processor.
Share Unit of Work Select this check box to share the unit of work between the parent exchange and each recipient exchange. See the same option of cSplitter for more information.

Usage

Usage rule

cRecipientList is used as a middle component in a Route.

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!