anchor.diff:  Boolean bool = XPathBuilder.xpath("foo/bar").evaluate(context, "<foo><bar>true</bar></foo>", Boolean.class);
   ----
   
  -Evaluating with a String result is a common requirement and thus you can
  -do it a bit simpler:
  +Evaluating with a `String` result is a common requirement and make this simpler:
   
   [source,java]
   ----
  
positive.code: 
  == Using XPathBuilder without an Exchange
  
  You can now use the `org.apache.camel.builder.XPathBuilder` without the
  need for an Exchange. This comes handy if you want
  to use it as a helper to do custom xpath evaluations.
  
  It requires that you pass in a CamelContext
  since a lot of the moving parts inside the XPathBuilder requires access
  to the Camel Type Converter and hence why
  CamelContext is needed.
  
  For example you can do something like this:
  
  [source,java]
  ----
  
negative.code: == Loading script from external resource
  
  You can externalize the script and have Camel load it from a resource
  such as `"classpath:"`, `"file:"`, or `"http:"`.
  This is done using the following syntax: `"resource:scheme:location"`,
  eg to refer to a file on the classpath you can do:
  
  [source,java]
  