Skip to main content Skip to complementary content

cMessageRouter Standard properties

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

The Standard cMessageRouter component belongs to the Routing family.


Usage rule

cMessageRouter is used as a middle component in a Route. It can only have one input channel but multiple output channels. Messages can be outputted through either a When, Otherwise or Route types of connection.

Connections Row / Route: Select this link to pass on all the messages to the next component.

Trigger / When: Select the When link and click the Component view.

In the Type list, select the type of language you will use to declare your condition from none, bean, constant, correlation, el, groovy, header, sql, jsonpath, jxpath, mvel, ognl, php, property, python, ruby, simple, Spel, sql, xpath, and xquery.

Append endChoice(): If the When link is followed by a cMessageFilter or cLoadBalancer and so on, there will be a compile error. This is because once there is such a component there, the flow type will change from choice() to loadbalance(), which can not be followed by a When or Otherwise link. Select this check box to change the flow type back from loadbalance() to choice().

In the Condition field, type in the condition that will be used to filter the messages.

All the messages that do not match this condition are retrieved with the Otherwise link to a different channel or dropped if an Otherwise link does not present.

Information noteNote:

There can be more than one When link in a Route.


Trigger / Otherwise: This link automatically retrieves the messages that do not match the When conditions.

Information noteNote:

There can be only one Otherwise link, which is optional, in a Route.


It is recommended not to put any message handling after the When or the Otherwise link. Always use a Mock/Direct endpoint to replace them and make a new Route to handle the messages.

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 – let us know how we can improve!