anchor.diff:  
   This will match the given predicate.
   
  -You can also evaluate for example as shown in the following three
  -examples:
  +You can also evaluate as shown in the following three examples:
   
   [source,java]
   ----
  
positive.code: xref:manual::expression.adoc[Expression] or xref:manual::predicate.adoc[Predicate] to be
  used in the xref:manual::dsl.adoc[DSL].
  
  For example you could use XPath to create an
  Predicate in a xref:{eip-vc}:eips:filter-eip.adoc[Message
  Filter] or as an Expression for a
  xref:{eip-vc}:eips:recipientList-eip.adoc[Recipient List].
  
  *Streams*
  
  If the message body is stream based, which means the input it receives
  is submitted to Camel as a stream. That means you will only be able to
  read the content of the stream *once*. So often when you use
  xref:xpath-language.adoc[XPath] as xref:xpath-language.adoc[Message Filter] or
  Content Based Router then you need to
  access the data multiple times, and you should use
  Stream Caching or convert the message body to
  a `String` prior which is safe to be re-read multiple times.
  
  [source,java]
  ----
  from("queue:foo").
    filter().xpath("//foo")).
    to("queue:bar")
  ----
  
  [source,java]
  ----
  from("queue:foo").
    choice().xpath("//foo")).to("queue:bar").
    otherwise().to("queue:others");
  ----
  
  == XPath Language options
  
  
negative.code: 
  Therefore, the utmost we can do is assist you in debugging such issues
  by adding two new features to the XPath Expression Language and are thus
  accessible from both predicates and expressions.
  
  === Logging the Namespace Context of your XPath expression/predicate
  
  Every time a new XPath expression is created in the internal pool, Camel
  will log the namespace context of the expression under the
  `org.apache.camel.language.xpath.XPathBuilder` logger. Since Camel
  represents Namespace Contexts in a hierarchical fashion (parent-child
  relationships), the entire tree is output in a recursive manner with the
  following format:
  
  [source,text]
  ----
  [me: {prefix -> namespace}, {prefix -> namespace}], [parent: [me: {prefix -> namespace}, {prefix -> namespace}], [parent: [me: {prefix -> namespace}]]]
  ----
  
  Any of these options can be used to activate this logging:
  
  *  Enable TRACE logging on the
  `org.apache.camel.language.xpath.XPathBuilder` logger, or some parent
  logger such as `org.apache.camel` or the root logger
  *  Enable the `logNamespaces` option as indicated in the following section,
  in which case the logging will occur on the INFO level
  
  === Auditing namespaces
  
  Camel is able to discover and dump all namespaces present on every
  incoming message before evaluating an XPath expression, providing all
  