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 df565132f9014f861750cec30e68990812082386
Author: Otavio Rodolfo Piske <angusyo...@gmail.com>
AuthorDate: Wed Feb 21 14:06:13 2024 +0100
CAMEL-20410: documentation fixes for camel-mvel
- Fixed samples
- Fixed grammar and typos
- Fixed punctuation
- Added and/or fixed links
- Converted to use tabs
---
components/camel-mvel/src/main/docs/mvel-component.adoc | 9 ++++-----
components/camel-mvel/src/main/docs/mvel-language.adoc | 13 ++++++-------
2 files changed, 10 insertions(+), 12 deletions(-)
diff --git a/components/camel-mvel/src/main/docs/mvel-component.adoc
b/components/camel-mvel/src/main/docs/mvel-component.adoc
index 239b603b457..5cc6bf21c1a 100644
--- a/components/camel-mvel/src/main/docs/mvel-component.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-component.adoc
@@ -38,8 +38,7 @@ mvel:templateName[?options]
---------------------------
Where *templateName* is the classpath-local URI of the template to
-invoke; or the complete URL of the remote template (eg:
-\file://folder/myfile.mvel).
+invoke; or the complete URL of the remote template (e.g.:
`\file://folder/myfile.mvel`).
// component-configure options: START
@@ -80,14 +79,14 @@ Camel will provide exchange information in the MVEL context
(just a
The mvel template resource is, by default, hot reloadable for both file
and classpath resources (expanded jar). If you set `contentCache=true`,
Camel will only load the resource once, and thus hot reloading is not
-possible. This scenario can be used in production, when the resource
+possible. This scenario can be used in production when the resource
never changes.
== Dynamic templates
Camel provides two headers by which you can define a different resource
location for a template, or the template content itself. If any of these
-headers is set then Camel uses this over the endpoint configured
+headers is set, then Camel uses this over the endpoint configured
resource. This allows you to provide a dynamic template at runtime.
// component headers: START
@@ -117,7 +116,7 @@ from("direct:in").
to("mvel:dummy?allowTemplateFromHeader=true");
-------------------------------------------------------------------------
-To specify a template directly as a header the component should use
+To specify a template directly as a header, the component should use
dynamically via a header, so for example:
[source,java]
diff --git a/components/camel-mvel/src/main/docs/mvel-language.adoc
b/components/camel-mvel/src/main/docs/mvel-language.adoc
index cf5007f1d42..94ea93e9476 100644
--- a/components/camel-mvel/src/main/docs/mvel-language.adoc
+++ b/components/camel-mvel/src/main/docs/mvel-language.adoc
@@ -18,7 +18,7 @@ MVEL is powerful for templates, but can also be used for
xref:manual::expression.adoc[Expression] or
xref:manual::predicate.adoc[Predicate]
For example, you can use MVEL in a xref:manual::predicate.adoc[Predicate]
-with the xref:eips:choice-eip.adoc[Content Based Router] EIP.
+with the xref:eips:choice-eip.adoc[Content-Based Router] EIP.
You can use MVEL dot notation to invoke operations. If you for instance
have a body that contains a POJO that has a `getFamilyName` method then
@@ -92,10 +92,10 @@ And in XML:
== Loading script from external resource
-You can externalize the script and have Camel load it from a resource
+You can externalize the script and have Apache Camel load it from a resource
such as `"classpath:"`, `"file:"`, or `"http:"`.
This is done using the following syntax: `"resource:scheme:location"`,
-e.g. to refer to a file on the classpath you can do:
+e.g., to refer to a file on the classpath you can do:
[source,java]
----
@@ -104,12 +104,11 @@ e.g. to refer to a file on the classpath you can do:
== Dependencies
-To use MVEL in your camel routes you need to add the dependency on
+To use MVEL in your Camel routes, you need to add the dependency on
*camel-mvel* which implements the MVEL language.
-If you use maven you could just add the following to your pom.xml,
-substituting the version number for the latest & greatest release (see
-the download page for the latest versions).
+If you use Maven, you could add the following to your `pom.xml`,
+substituting the version number for the latest & greatest release.
[source,xml]
----
