THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
For example, in the route below we intercept sending a message to the mock:foo endpoint and detour the message.Wiki Markup
...
...
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.
The Camel team plan for Camel 3.0 to support this as internal refactorings in the routing engine is needed to support this properly.
...
...
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.
...
...
From Camel 2.9: it's recommended to override the isUseAdviceWith() method and return true to tell Camel you are using advice with in your unit tests. Then after you have done the adviceWith(), then you must start CamelContext manually. See further below for an example.
Using AdviceWithRouteBuilder
...
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: foo, foobar, 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 foo and bar.
...
...
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.
For example:
...
...
To match the foo queue and disregard any options.
Using weaveById
The weaveById allows you to manipulate the route, for example by replacing a node with other nodes.
...
For example given the following route:
...
...
Then let's go over the four methods to see how you can use them in unit tests:Wiki Markup .to("mock:bar").id("bar") with the .multicast().to("mock:a").to("mock:b").
That means instead of sending the message to a mock:bar endpoint, we do a Multicast to mock:a and mock:b endpoints instead.Wiki Markup .to("mock:bar").id("bar").Wiki Markup to("mock:a").transform(constant("Bye World")) before the node with the id bar.
That means the message being send to mock:bar would have been transformed to a constant message "Bye World".Wiki Markup to("mock:a").transform(constant("Bye World")) after the node with the id bar.
...
For example to replace any nodes which has "foo" you can doWiki Markup ".foo." in the pattern to match that "foo" is present anywhere in the string.
...
For example to remove a transform from the following route:Wiki Markup Wiki Markup
Using Selectors
Available os of Camel 2.8
...
For example to remove the first .to node in route you can do as follows:
...
...
Using weaveAddFirst / weaveAddLast
...
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:
...
...
Replace from With Another Endpoint
...
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 seda:foo endpoint:
...
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.
...
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.Wiki Markup