Available as of Camel 2.1
AdviceWith is used for testing Camel routes where you can advice an existing route before its being tested. What
For example, in the route below we intercept sending a message to the
It is recommended to only advice a given route once (you can of course advice multiple routes). If you do it multiple times, then it may not work as expected, especially when any kind of error handling is involved.
It's recommended to only advice routes which are not started already. If you advice already started routes, then it may not work as expected.
Telling Camel you are using adviceWith
From Camel 2.9: it's recommended to override the
Is used to easily mock all endpoints. See more details and examples at Mock.
Is used to easily mock endpoints using a pattern. See more details and examples at Mock. See below for pattern matching. From Camel 2.10 onwards you can specify multiple patterns.
Is used to easily mock endpoints using a pattern, and skip sending to the original endpoint. See more details and examples at Mock. See below for pattern matching. You can specify multiple patterns.
Is used to select node(s) matching by id's, and weave in the following nodes. See below for pattern matching and examples.
Is used to select nodes(s) matching by their
Camel 2.8: Is used to select node(s) matching by their class type (the classes from the
Camel 2.8: Is a short hand to easily weave in the following nodes in the start of the route.
Camel 2.8: Is a short hand to easily weave in the following nodes in the end of the route.
Camel 2.9: To replace the route input with a new endpoint URI.
pattern option is used for matching. It uses the same rules as the Intercept, which is applied in the following order:
- match exact
- match by wildcard
- match by regular expression
For example to match exact you can use
weaveById("foo") which will match only the id in the route which has the value:
foo. The wildcard is when the pattern ends with a
* character, such as:
weaveById("foo*") which will match any id's starting with
foo, such as:
foobie and so forth. The regular expression is more advanced and allows you to match multiple ids, such as
weaveById("(foo|bar)") which will match both
If you try to match a
pattern on an exact endpoint URI, then mind that URI options ordering may influence, and hence its best to match by wildcard.
To match the
foo queue and disregard any options.
weaveById allows you to manipulate the route, for example by replacing a node with other nodes.
The following methods are available:
Removes the selected node(s).
Replaces the selected node(s) with the following nodes.
Before the selected node(s), the following nodes is added.
After the selected node(s), the following nodes is added.
For example given the following route:
Then let's go over the four methods to see how you can use them in unit tests:In this example we replace the
That means instead of sending the message to a
mock:barendpoint, we do a Multicast to
mock:bendpoints instead. In the example above, we simply just remove the
.to("mock:bar").id("bar"). In the example above, we add the following nodes
to("mock:a").transform(constant("Bye World"))before the node with the id
That means the message being send to
mock:barwould have been transformed to a constant message "
Bye World". In the example above, we add the following nodes
to("mock:a").transform(constant("Bye World"))after the node with the id
weaveByToString also allows you to manipulate the route, for example by replacing a node with other nodes. As opposed to
weaveById, this method uses the
toString representation of the node(s) when matching. This allows you to match nodes, which may not have assigned ids, or to match EIP pattern. You have to be a bit more careful when using this as the
toString representation can be verbose and contain characters such as [ ] ( )-> and so forth. That is why using the regular expression matching is the must usable.
weaveByToString has the same methods as
For example to replace any nodes which has
"foo" you can do
".foo."in the pattern to match that
"foo"is present anywhere in the string.
Available as of Camel 2.8
weaveByToType also allows you to manipulate the route, for example by replacing a node with other nodes. As opposed to
weaveByToString this method uses the class type of the node(s) when matching. This allows you to match EIP pattern by its type.
weaveByToType has the same methods as
For example to remove a transform from the following route:You can do:
Available os of Camel 2.8
The following methods
weaveByType(Class) each match N+ nodes. By using optional selectors you can narrow down the nodes being used. For example if
weaveByType(Class) returns 2 nodes. Then you can use a selector to indicate it should only select the first node.
Will only select the first matched node.
Will only select the last matched node.
Will only select the N'th matched node. The index is zero-based.
Will only select the matches node within the given range by index (both inclusive). The index is zero-based.
|Camel 2.14.2/2.15: To limit the selection to at most N level deep in the Camel route tree. The first level is starting from number 1. So number 2 is the children of the 1st level nodes.|
For example to remove the first
.to node in route you can do as follows:
Available as of Camel 2.8
weaveAddLast is a shorthand to easily add nodes to the route. These methods can only add to an existing routes. If you want to manipulate the route, then there are plenty of methods as already shown on this page.
For example if you want to send a message to a
mock:input endpoint you can do as follows:
Likewise if you want to easily send a message to a
mock:output endpoint you can do as follows:
You can of course combine those in the same advice with:
from With Another Endpoint
Available as of Camel 2.9
You may have routes which consumes messages from endpoints which you want to substitute with another endpoint for easier unit testing. For example a JMS endpoint could be replaced with a SEDA or Direct for unit testing a route, as shown below where we replace the input of the route to a
Using Mock Endpoints
While routing messages, you may want to easily know how the messages was routed. For example you can let Camel mock all endpoints, which mean that when a message is sent to any endpoint, its first send to a mock endpoint, and then afterwards to the original endpoint. Then from your unit tests, you can setup expectations on the mock endpoints.
See more details see: Mocking existing endpoints using the camel-test component at Mock.
Available as of Camel 2.9
It is recommended to override the method
isUseAdviceWith and return
true to instruct Camel that you are using
adviceWith in the unit tests. Then in your unit test methods, after you have done the
adviceWith you must start
CamelContext by invoke the
start method on the
context instance. In the following we have an example. The route is using ActiveMQ to route messages. What we would like to do in a unit test is to test the route, but without having to set and use ActiveMQ. We do not have ActiveMQ on the classpath. So for that we need to advice the route and replace ActiveMQ with for example a SEDA endpoint instead.