anchor.diff:    </camelContext>
   ----
   
  -There is a
  +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
  -http://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/test/resources/org/apache/camel/spring/processor/XsltTest-context.xml[its
  -Spring XML] if you want a concrete example.
  +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 then in Camel 2.2 or older it
  -uses the default `javax.xml.transform.URIResolver` which means it can
  -only lookup files from file system, and its does that relative from the
  +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 this include:
  +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"/>
   ----
   
  -Will lookup the `staff_tempkalte.xsl` file from the starting folder
  -where the application was started.
  -
   *Camel 2.3 or newer*  +
  - Now Camel provides its own implementation of `URIResolver` which allows
  -Camel to load included files from the classpath and more intelligent
  -than before.
  -
  -For example this include:
  + 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"/>
   ----
   
  -Will now be located relative from the starting endpoint, which for
  -example could be:
  +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]
   ----
  -.to("xslt:org/apache/camel/component/xslt/staff_include_relative.xsl")
  -----
  -
  -Which means Camel will locate the file in the *classpath* as
  -`org/apache/camel/component/xslt/staff_template.xsl`. +
  - This allows you to use xsl include and have xsl files located in the
  -same folder such as we do in the example
  -`org/apache/camel/component/xslt`.
  -
  -You can use the following two prefixes `classpath:` or `file:` to
  -instruct Camel to look either in classpath or file system. If you omit
  -the prefix then Camel uses the prefix from the endpoint configuration.
  -If that neither has one, then classpath is assumed.
  -
  -You can also refer back in the paths such as
  -
  -[source,java]
  -----
       <xsl:include href="../staff_other_template.xsl"/>
   ----
   
  -Which then will resolve the xsl file under `org/apache/camel/component`.
   
   === Using xsl:include and default prefix
   
  -When using xsl:include such as:
  -
  -[source,xml]
  -----
  -<xsl:include href="staff_template.xsl"/>
  -----
  -
  -Then in Camel 2.10.3 and older, then Camel will use "classpath:" as the
  -default prefix, and load the resource from the classpath. This works for
  -most cases, but if you configure the starting resource to load from
  -file,
  -
  -[source,java]
  -----
  -.to("xslt:file:etc/xslt/staff_include_relative.xsl")
  -----
  -
  -.. then you would have to prefix all your includes with "file:" as well.
  -
  -[source,xml]
  -----
  -<xsl:include href="file:staff_template.xsl"/>
  -----
  -
  -From Camel 2.10.4 onwards we have made this easier as Camel will use the
  -prefix from the endpoint configuration as the default prefix. So from
  -Camel 2.10.4 onwards you can do:
  -
  -[source,xml]
  -----
  -<xsl:include href="staff_template.xsl"/>
  -----
  -
  -Which will load the staff_template.xsl resource from the file system, as
  -the endpoint was configured with "file:" as prefix. +
  - You can still though explicit configure a prefix, and then mix and
  -match. And have both file and classpath loading. But that would be
  -unusual, as most people either use file or classpath based resources.
  +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
   
  
positive.code: ----
  xslt:templateName[?options]
  ----
  
  Where *templateName* is the classpath-local URI of the template to
  invoke; or the complete URL of the remote template. Refer to the
  http://static.springframework.org/spring/docs/2.5.x/api/org/springframework/core/io/DefaultResourceLoader.html[Spring
  Documentation for more detail of the URI syntax]
  
  You can append query options to the URI in the following format,
  `?option=value&option=value&...`
  
  Here are some example URIs
  
  URI
  
  Description
  
  [source]
  ----
  xslt:com/acme/mytransform.xsl
  ----
  
  refers to the file com/acme/mytransform.xsl on the classpath
  
  [source]
  ----
  xslt:file:///foo/bar.xsl
  ----
  
  refers to the file /foo/bar.xsl
  
  [source]
  ----
  xslt:http://acme.com/cheese/foo.xsl
  ----
  
  refers to the remote http resource
  
  Maven users will need to add the following dependency to their `pom.xml`
  for this component when using *Camel 2.8* or older:
  
  [source,xml]
  ----
  
negative.code:   to("xslt:com/acme/mytransform.xsl");
  ----
  
  
  If you want to use InOnly and consume the message and send it to another
  destination you could use the following route:
  