Double-click the cBeanRegister component
labeled appendAggregator to display its
Basic settings view in the Component tab.
In the Id field, enter
"appendAggregator". Select the Simple option and in the Class
Name field, enter the name of the predefined Java bean,
beans.AppendAggregator in this scenario, which will be
called later by the cSplitter
component.
Double-click the cTimer component labeled
Starter to display its Basic settings view in the Component tab.
In the Repeat field, enter 1
to trigger the message exchange. Keep the default settings of the other
options.
Double-click the cSetbody component
labeled Set_body to display its Basic settings view in the Component tab.
Select SIMPLE in the Language list and enter "thing1, thing2,
thing3" in the Expression field
as the message body.
Configure the cSetbody component labeled
Set_new_body in the same way to set
new body to the sub-messages. In the Expression field, enter *** SPLIT: ${body} to
add *** SPLIT: before the old message body.
Double-click the cSplitter component to
display its Basic settings view in the
Component tab.
In this use case, we want to split the message body into sub-messages
using , as the separator.
Select Simple in the Language list and enter ${body} in
the Expression field.
Select the Use Strategy check box. In the
Strategy field, enter the Id of the
preregistered Java bean appendAggregator, which will be
used to aggregate the replies from sub-messages.
Double-click the cDirect component
labeled directA_sender to display its
Basic settings view in the Component tab.
Click [...] and select the directA_receiver node to receive the
sub-messages.
Double-click the cDirect component
labeled directA_receiver to display its
Basic settings view in the Component tab.
In the Name field, type in
"directA" to identify this endpoint.
Keep the default settings of the cLog
components labeled Log_Finished and
Log_Split. Log_Finished will
log the aggregated replies from sub-messages. Log_Split
will log the sub-messages.
Press Ctrl+S to save your Route.
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!