anchor.diff:  </xsl:template>
   ----
   
  -This information is not available on the Exchange stored as an Exception
  -that contains the message in the `getMessage()` method on the exception.
   The exception is stored on the Exchange as a warning with the
   key `Exchange.XSLT_WARNING.`
   
  
positive.code: <to uri="xslt:MyTransform.xsl"/>
  ----
  
  And the XSLT just needs to declare it at the top level for it to be
  available:
  
  [source,xml]
  
negative.code:   </camelContext>
  ----
  
  To see an example, look at the 
  http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/java/org/apache/camel/spring/processor/XsltTest.java[test
  case] along with its 
  http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/XsltTest-context.xml[
  Spring XML].
  
  === Using xsl:include
  
  *Camel 2.2 or older* +
  If you use `xsl:include` in your XSL files in *Camel 2.2 or older*, the default `javax.xml.transform.URIResolver` is used. Files will be resolved relative to the
  JVM starting folder.
  
  For example the following include statement will look up the `staff_template.xsl` file starting from the folder where the application was started.
  
  [source,xml]
  ----
  <xsl:include href="staff_template.xsl"/>
  ----
  
  *Camel 2.3 or newer*  +
   For Camel 2.3 or newer, Camel provides its own implementation of `URIResolver`. This allows
  Camel to load included files from the classpath.
  
  For example the include file in the following code will be located relative to the starting endpoint.
  
  [source,xml]
  ----
  <xsl:include href="staff_template.xsl"/>
  ----
  
  This means that Camel will locate the file in the *classpath* as
  *org/apache/camel/component/xslt/staff_template.xsl* +
   
  You can use `classpath:` or `file:` to instruct Camel to look either in the classpath or file system. If you omit
  the prefix then Camel uses the prefix from the endpoint configuration.
  If no prefix is specified in the endpoint configuration, the default is `classpath:`.
  
  You can also refer backwards in the include paths. In the following example, the xsl file will be resolved  under `org/apache/camel/component`.
  
  [source,java]
  ----
      <xsl:include href="../staff_other_template.xsl"/>
  ----
  
  
  === Using xsl:include and default prefix
  
  In *Camel 2.10.3 and older*, `classpath:` is used as the default prefix. +
  If you configure the starting resource to load using `file:` then all subsequent incudes will have to be prefixed with `file:`.
  
  From *Camel 2.10.4*, Camel will use the prefix from the endpoint configuration as the default prefix.
  
  You can explicitly specify `file:` or `classpath:` loading. The two loading types can be mixed in a XSLT script, if necessary.
  
  === Using Saxon extension functions
  
  