anchor.diff:  TIP: You can also use `mockEndpoints` to auto mock instead of `weaveByToUri` in the example above.
   The `weave` methods has a lot more power to manipulate the route, such as message transformation, routing the message or much more.
   
  -==== weaveAddFirst and weaveAddLast
  +=== weaveAddFirst and weaveAddLast
   
   The `weaveAddFirst` and `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 use the other `weave` methods as already covered.
  
positive.code: 
  IMPORTANT: Before using `adviceWith` then it is best to tell Camel that advice is in use, which is covered in the following section.
  
  === Turning on advice during testing
  
  When `adviceWith` is being used, then Camel will restart the adviced routes. This happens
  because the route is manipulated, and Camel needs to:
  
negative.code: Here we weave and select the xref:{eip-vc}:eips:split-eip.adoc[Split] EIP and weave in a message transformation, that
  is processed before calling the splitter. This means the message body is appended with _Camel is awesome_.
  
  === weaveByToUri
  
  The `weaveByToUri` is a handy method that makes it easy to _weave_ a Camel route that
  send messages to a given endpoint URI or pattern.
  