This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
commit f504110cf189f89ffe9fdf301fbcf0c5e7138bab
Author: Otavio Rodolfo Piske <angusyo...@gmail.com>
AuthorDate: Wed Feb 21 13:12:11 2024 +0100
CAMEL-20410: documentation fixes for camel-xslt-saxon
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
.../src/main/docs/xslt-saxon-component.adoc | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git
a/components/camel-xslt-saxon/src/main/docs/xslt-saxon-component.adoc
b/components/camel-xslt-saxon/src/main/docs/xslt-saxon-component.adoc
index 5b22938760e..53888f622a6 100644
--- a/components/camel-xslt-saxon/src/main/docs/xslt-saxon-component.adoc
+++ b/components/camel-xslt-saxon/src/main/docs/xslt-saxon-component.adoc
@@ -72,7 +72,7 @@ from("activemq:My.Queue").
If you want to use InOnly and consume the message and send it to another
-destination you could use the following route:
+destination, you could use the following route:
[source,java]
----
@@ -107,7 +107,7 @@ available:
== Spring XML versions
-To use the above examples in Spring XML you would use something like the
following code:
+To use the above examples in Spring XML, you would use something like the
following code:
[source,xml]
----
@@ -125,7 +125,7 @@ To use the above examples in Spring XML you would use
something like the followi
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.
+For example, the included file in the following code will be located relative
to the starting endpoint.
[source,xml]
----
@@ -136,10 +136,11 @@ 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.
+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`.
+You can also refer backwards in the included paths.
+In the following example, the xsl file will be resolved under
`org/apache/camel/component`.
[source,xml]
----
@@ -151,7 +152,7 @@ You can also refer backwards in the include paths. In the
following example, the
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.
+You can explicitly specify `file:` or `classpath:` loading. The two loading
types can be mixed in an XSLT script, if necessary.
== Using Saxon extension functions
@@ -194,7 +195,7 @@ With Spring XML:
== Dynamic stylesheets
-To provide a dynamic stylesheet at runtime you can either
+To provide a dynamic stylesheet at runtime, you can either:
- Define a dynamic URI. See
xref:manual:faq:how-to-use-a-dynamic-uri-in-to.adoc[How to use a dynamic URI in
to()] for more information.
@@ -220,7 +221,7 @@ to use, instead of referring to a file as the example from
above.
TIP: You can set `contentCache=false` and refer to a non-existing template,
such as `"xslt-saxon:dummy.xsl?contentCache=false&allowTemplateFromHeader=true"`
as this will tell Camel to not load `dummy.xsl` on startup but to load the
stylesheet on demand. And because you
-provide the stylesheet via headers then its fully dynamic.
+provide the stylesheet via headers, then its fully dynamic.
== Accessing warnings, errors and fatalErrors from XSLT ErrorListener
@@ -230,7 +231,7 @@ keys `Exchange.XSLT_ERROR`, `Exchange.XSLT_FATAL_ERROR`,
or `Exchange.XSLT_WARNING` which allows end users to get hold of any
errors happening during transformation.
-For example in the stylesheet below, we want to determinate whether a staff has
+For example, in the stylesheet below, we want to determinate whether a staff
has
an empty dob field. And to include a custom error message using
xsl:message.
