anchor.diff:  ----
   
   You can also refer to a specific thread pool
  -to be used, using the executorServiceRef option
  +to be used, using the `executorServiceRef` option
   
   [source,xml]
   ----
  
positive.code:     .to("mock:result");
  ----
  
  [[OnCompletion-UsingonCompletionfromSpringDSL.1]]
  === Using onCompletion from Spring DSL
  
  This works just like the route scope except from the fact that they are
  defined globally. An example below:
  
  [source,xml]
  ----
  
negative.code: [[OnCompletion-OnCompletion]]
  = OnCompletion
  
  Camel has this concept of a _Unit of Work_ that encompass the
  Exchange. The unit of work among others supports
  synchronization callbacks that are invoked when the
  Exchange is complete. The callback API is defined in
  `org.apache.camel.spi.Synchronization` and the extended synchronization
  `org.apache.camel.spi.SynchronizationRouteAware` that have callbacks for
  route events.
  
  == UnitOfWork API
  
  You can get hold of the `org.apache.camel.spi.UnitOfWork` from
  `org.apache.camel.Exchange` with the method `getUnitOfWork()`.
  
  == OnCompletion DSL
  
  The OnCompletion EIP supports the following features:
  
  * level: context or route (route level override global level)
  * triggered either always, only if completed with success, or only if failed
  * `onWhen` predicate to only trigger if matched
  * `mode` to define whether to run either before or after
  route consumer writes response back to callee (if its InOut) (default AfterConsumer)
  