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

The Standard
cRoutingSlip component belongs to the Routing family.

Basic settings

Usage

This use case requires a cFile component as the
message sender, a cSetHeader component to define a
series of endpoints, a cRoutingSlip component to
route messages to the endpoints consecutively, three cMessagingEndpoint components to retrieve messages routed to the
endpoints, and three cProcessor components to
monitor messages routed to the connected messaging endpoints.

1. From the Palette, expand the Connectivity folder, drop one cFile and three cMessagingEndpoint components onto the design workspace, and
   label them to better identify their roles in the Route, as shown
   above.
2. From the Core folder, drop a cSetHeader component onto the design workspace, and label it
   to better identify its role in the Route.
3. From the Routing folder, drop a cRoutingSlip component onto the design workspace,
   and label it to better identify its role in the Route.
4. From the Custom folder, drop three cProcessor components onto the design workspace, and label
   them to better identify their roles in the Route.
5. Right-click the cFile component, select
   Row > Route from the contextual menu and click the cSetHeader component.
6. Right-click the cSetHeader component,
   select Row > Route from the contextual menu and click the cRoutingSlip component.
7. Repeat this operation to connect the cMessagingEndpoint components to the corresponding cProcessor components.

1. Double-click the cFile component, which
   is labelled Sender, to display its Basic settings view in the Component tab.
   

2. In the Path field, fill in or browse to the path to the
   folder that holds the source files Beijing.xml, London.xml,
   Paris.xml, and Washington.xml.
   From the Encoding list, select the
   encoding type of your source files. Leave the other parameters as they
   are.
3. Double-click the cSetHeader component,
   which is labelled Set_endpoints, to
   display its Basic settings view in the
   Component tab.
   

4. Click [+] to add a row to the Headers table.
   In the Name field, type in the name of
   the header you want to add to each message.
   In this use case, we simply use mySlip, which is the
   default value filled in the Header name
   field of the cRoutingSlip component.
5. From the Language list box, select the Constant or Simple, and in the Value
   field, type in the URIs you wish the message to be routed consecutively to,
   separated by a comma, which is the default value of the URI delimiter field of the cRoutingSlip component.
   In this use case, we want the message to be routed first to endpoint
   c, then to endpoint a, and
   finally to endpoint b.
6. Double-click the cRoutingSlip component,
   which is labelled Routing_slip, to
   display its Basic settings view in the
   Component tab, and define the message
   header in the Header name field and the URI
   delimiter in the URI delimiter field.
   In this use case, we simply use the default settings.
   

7. Double-click the cMessagingEndpoint
   component labelled Endpoint_a to display its Basic settings view in the Component tab, and type in the URI in the URI field for the destination of your messages.
   Here, we want to use this component to retrieve the message routed to the
   URI direct:a.
   

   Repeat this step to set the endpoint URIs in the other cMessagingEndpoint components:
   direct:b and direct:c
   respectively.
8. Double-click the cProcessor component,
   which is labelled Monitor_a, to display
   its Basic settings view in the Component tab, and customize the code so that the
   console will display information the way you wish.
   Here, we want to use this component to monitor the messages routed to the
   connected endpoint a and display the file name, so we
   customize the code accordingly, as follows:
   System.out.println("Message received on endpoint a: "+ exchange.getIn().getHeader("CamelFileName"));

   1 2	System.out.println("Message received on endpoint a: "+ exchange.getIn().getHeader("CamelFileName"));

   Repeat this step to customize the code for the other two cProcessor components, for messages routed to the
   connected endpoints b and c
   respectively.
   System.out.println("Message received on endpoint b: "+ exchange.getIn().getHeader("CamelFileName"));

   1 2	System.out.println("Message received on endpoint b: "+ exchange.getIn().getHeader("CamelFileName"));

   System.out.println("Message received on endpoint c: "+ exchange.getIn().getHeader("CamelFileName"));

   1 2	System.out.println("Message received on endpoint c: "+ exchange.getIn().getHeader("CamelFileName"));

9. Press Ctrl+S to save your Route.

1. Click the Code tab at the bottom of the
   design workspace to have a look at the generated code.
   

   In this partially shown code, messages from the sender are given a header
   according to .setHeader, which carries a list of URIs
   ("direct:c,direct:a,direct:b"), and then routed in the slip
   pattern according by cRoutingSlip_1.
2. Click the Run view to display it and
   click the Run button to launch the
   execution of your Route.
   You can also press F6 to execute it.
   

   RESULT: The source file messages are routed consecutively to the defined
   endpoints: c, then a, and then
   b.

In this scenario, we will reuse the Route set up in the previous scenario, without
adding or removing any components or modifying any connections.

1. Double-click the cSetHeader component to
   display its Basic settings view in the
   Component tab.
   

2. Select Bean from the Language list box, and in the Value field, specify the Java Bean that will return the
   endpoint URIs. In this use case, type in:
   beans.setEndpoints
3. Press Ctrl+S to save your Route.

1. Click the Code tab at the bottom of the
   design workspace to have a look at the generated code.
   

   In this partially shown code, messages from the sender are given a header
   according to .setHeader, which carries a list of URIs returned
   by the beans.setEndpoints.class, and then routed to the
   cRoutingSlip_1.
2. Click the Run view to display it and
   click the Run button to launch the
   execution of your Route.
   You can also press F6 to execute it.
   

   RESULT: The sources are routed consecutively to the defined endpoints: the
   message containing the city name Beijing is routed
   first to endpoint c, then to endpoint
   a, and finally to endpoint b;
   the message containing the city name Paris is routed
   first to endpoint a, then to endpoint
   b, and finally to endpoint c;
   the other messages are routed to endpoint b and then to
   endpoint c.