From 598a3524dbdf04e5a20acb039a7d3e7148848887 Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:23:05 +0100 Subject: [PATCH 01/11] CAMEL-20410: documentation fixes for camel-jq - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- components/camel-jq/src/main/docs/jq-language.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/components/camel-jq/src/main/docs/jq-language.adoc b/components/camel-jq/src/main/docs/jq-language.adoc index 5f876cfaad84e..7031bdee5abed 100644 --- a/components/camel-jq/src/main/docs/jq-language.adoc +++ b/components/camel-jq/src/main/docs/jq-language.adoc @@ -22,7 +22,7 @@ include::partial$language-options.adoc[] == Examples -For example, you can use JQ in a xref:manual::predicate.adoc[Predicate] with the xref:eips:choice-eip.adoc[Content Based Router] EIP. +For example, you can use JQ in a xref:manual::predicate.adoc[Predicate] with the xref:eips:choice-eip.adoc[Content-Based Router] EIP. [source,java] ---- @@ -45,7 +45,7 @@ To enable camel-jackson POJO type conversion, refer to the Camel Jackson documen By default, JQ uses the message body as the input source. However, you can also use a header as input by specifying the `headerName` option. -For example to count the number of books from a JSON document that was stored in a header named `books` you can do: +For example, to count the number of books from a JSON document that was stored in a header named `books` you can do: [source,java] ---- @@ -61,9 +61,9 @@ NOTE: JQ comes with about a hundred built-in functions, and you can see many exa The camel-jq adds the following functions: -* `header` - Allow to access the Message header in a JQ expression. -* `property` - Allow to access the Exchange property in a JQ expression. -* `constant` - Allow to use a constant value as-is in a JQ expression. +* `header`: allow accessing the Message header in a JQ expression. +* `property`: allow accessing the Exchange property in a JQ expression. +* `constant`: allow using a constant value as-is in a JQ expression. For example, to set the property foo with the value from the Message header `MyHeader': @@ -97,7 +97,7 @@ from("direct:start") == Transforming a JSon message -For basic JSon transformation where you have a fixed structure you can represent with a combination of using +For basic JSon transformation where you have a fixed structure, you can represent with a combination of using Camel simple and JQ language as: [source] From 47b3c40da82f08bfb6c7831bf3cc97e665485a46 Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:24:29 +0100 Subject: [PATCH 02/11] CAMEL-20410: documentation fixes for camel-jsch - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- components/camel-jsch/src/main/docs/scp-component.adoc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/components/camel-jsch/src/main/docs/scp-component.adoc b/components/camel-jsch/src/main/docs/scp-component.adoc index 9fa2ff5cdc398..fd76836e67cff 100644 --- a/components/camel-jsch/src/main/docs/scp-component.adoc +++ b/components/camel-jsch/src/main/docs/scp-component.adoc @@ -14,7 +14,7 @@ *{component-header}* -The Camel-Jsch component supports the +The Camel Jsch component supports the http://en.wikipedia.org/wiki/Secure_copy[SCP protocol] using the Client API of the http://www.jcraft.com/jsch/[Jsch] project. Jsch is already used in camel by the xref:ftp-component.adoc[FTP] component for the *sftp:* @@ -60,10 +60,9 @@ include::partial$component-endpoint-options.adoc[] == Limitations -Currently camel-jsch only supports a +Currently, camel-jsch only supports a https://www.javadoc.io/doc/org.apache.camel/camel-api/current/org/apache/camel/Producer.html[Producer] -(i.e. copy files to another host). - +(i.e., copy files to another host). include::spring-boot:partial$starter.adoc[] From cef441d8ea2542835751bb92e5e5dde5166e00de Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:26:48 +0100 Subject: [PATCH 03/11] CAMEL-20410: documentation fixes for camel-jslt - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../camel-jslt/src/main/docs/jslt-component.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/components/camel-jslt/src/main/docs/jslt-component.adoc b/components/camel-jslt/src/main/docs/jslt-component.adoc index 78cd3e0b397db..7d3666413339b 100644 --- a/components/camel-jslt/src/main/docs/jslt-component.adoc +++ b/components/camel-jslt/src/main/docs/jslt-component.adoc @@ -14,7 +14,7 @@ *{component-header}* -The Jslt component allows you to process a JSON messages using an +The JSLT component allows you to process JSON messages using an https://github.com/schibsted/jslt[JSLT] expression. This can be ideal when doing JSON to JSON transformation or querying data. @@ -40,7 +40,7 @@ jslt:specName[?options] Where *specName* is the classpath-local URI of the specification to invoke; or the complete URL of the remote specification -(eg: \file://folder/myfile.vm). +(e.g.: `\file://folder/myfile.vm`). // component-configure options: START @@ -68,12 +68,12 @@ Camel can supply exchange information as variables when applying a JSLT expressi | name | value | headers | The headers of the In message as a json object | variables |The variables -| exchange.properties | The *Exchange* properties as a json object. _exchange_ is the name of the variable and _properties_ is the path to the exchange properties. Available if _allowContextMapAll_ option is true. +| exchange.properties | The *Exchange* properties as a json object. `exchange` is the name of the variable and `properties` is the path to the exchange properties. Available if `allowContextMapAll` option is true. |=== All the values that cannot be converted to json with Jackson are denied and will not be available in the jslt expression. -For example, the header named "type" and the exchange property "instance" can be accessed like +For example, the header named `type` and the exchange property `instance` can be accessed like [source,json] -------------------------------------- @@ -85,7 +85,7 @@ For example, the header named "type" and the exchange property "instance" can be == Samples -For example you could use something like +For example, you could use something like: [source,java] -------------------------------------- @@ -93,7 +93,7 @@ from("activemq:My.Queue"). to("jslt:com/acme/MyResponse.json"); -------------------------------------- -And a file based resource: +And a file-based resource: [source,java] --------------------------------------------------------------- @@ -103,7 +103,7 @@ from("activemq:My.Queue"). --------------------------------------------------------------- You can also specify which JSLT expression the component should use -dynamically via a header, so for example: +dynamically via a header, so, for example: [source,java] --------------------------------------------------------------------- From 9ef40ee1148e130b6b46c20bd22f1bb313e1ea2b Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:31:16 +0100 Subject: [PATCH 04/11] CAMEL-20410: documentation fixes for camel-json-patch - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../camel-json-patch/src/main/docs/json-patch-component.adoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/components/camel-json-patch/src/main/docs/json-patch-component.adoc b/components/camel-json-patch/src/main/docs/json-patch-component.adoc index 1df6208aac85f..4663c58af5a5d 100644 --- a/components/camel-json-patch/src/main/docs/json-patch-component.adoc +++ b/components/camel-json-patch/src/main/docs/json-patch-component.adoc @@ -14,9 +14,8 @@ *{component-header}* -The JsonPatch component allows you to process a JSON messages using an -https://github.com/schibsted/jslt[JSLT] expression. This can be -ideal when doing JSON to JSON transformation or querying data. +The JsonPatch component allows you to process JSON messages using an +https://github.com/java-json-tools/json-patch[JSON Patch] (https://datatracker.ietf.org/doc/html/rfc6902[RFC 6902]). Maven users will need to add the following dependency to their `pom.xml` for this component: From 058696285d73a66a97ace619556deb91da7b90f8 Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:32:25 +0100 Subject: [PATCH 05/11] CAMEL-20410: documentation fixes for camel-json-validator - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../src/main/docs/json-validator-component.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/components/camel-json-validator/src/main/docs/json-validator-component.adoc b/components/camel-json-validator/src/main/docs/json-validator-component.adoc index 02590de97b885..e2829ad669a04 100644 --- a/components/camel-json-validator/src/main/docs/json-validator-component.adoc +++ b/components/camel-json-validator/src/main/docs/json-validator-component.adoc @@ -15,7 +15,7 @@ *{component-header}* The JSON Schema Validator component performs bean validation of the message body -against JSON Schemas v4, v6, v7, v2019-09 draft and and v2020-12(partial) using the NetworkNT JSON Schema library +against JSON Schemas v4, v6, v7, v2019-09 draft and v2020-12(partial) using the NetworkNT JSON Schema library (https://github.com/networknt/json-schema-validator). Maven users will need to add the following dependency to their `pom.xml` @@ -59,7 +59,7 @@ include::partial$component-endpoint-options.adoc[] == Example -Assuming we have the following JSON Schema +Assuming we have the following JSON Schema: *myschema.json* @@ -101,7 +101,7 @@ Assuming we have the following JSON Schema } ---- -we can validate incoming JSON with the following Camel route, where `myschema.json` is loaded from the classpath. +We can validate incoming JSON with the following Camel route, where `myschema.json` is loaded from the classpath. [source,java] ---- @@ -112,7 +112,7 @@ from("direct:start") If you use the default schema loader, it will try to determine the schema version from the $schema property and instruct the https://github.com/networknt[validator] appropriately. If it can't find (or doesn't recognize) the $schema property, it will assume your schema is version https://json-schema.org/specification-links.html#draft-2019-09-formerly-known-as-draft-8[2019-09]. -If your schema is local to your application (e.g. a classpath location as opposed to URL), your schema can also contain $ref links to a relative subschema in the classpath. Per the JSON schema spec, your schema must not have an $id identifier property for this to work properly. See the https://github.com/apache/camel/blob/main/components/camel-json-validator/src/test/java/org/apache/camel/component/jsonvalidator/LocalRefSchemaTest.java[unit test] and https://github.com/apache/camel/blob/main/components/camel-json-validator/src/test/resources/org/apache/camel/component/jsonvalidator/Order.json[schema] for an example. +If your schema is local to your application (e.g. a classpath location as opposed to URL), your schema can also contain `$ref` links to a relative subschema in the classpath. Per the JSON schema spec, your schema must not have an $id identifier property for this to work properly. See the https://github.com/apache/camel/blob/main/components/camel-json-validator/src/test/java/org/apache/camel/component/jsonvalidator/LocalRefSchemaTest.java[unit test] and https://github.com/apache/camel/blob/main/components/camel-json-validator/src/test/resources/org/apache/camel/component/jsonvalidator/Order.json[schema] for an example. include::spring-boot:partial$starter.adoc[] From 4b1c88ba37e998568fe21a5814937c2e6451b92e Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:33:21 +0100 Subject: [PATCH 06/11] CAMEL-20410: documentation fixes for camel-jsonapi - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../camel-jsonapi/src/main/docs/jsonApi-dataformat.adoc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/components/camel-jsonapi/src/main/docs/jsonApi-dataformat.adoc b/components/camel-jsonapi/src/main/docs/jsonApi-dataformat.adoc index 5e45d0d19ef72..1262e7584404b 100644 --- a/components/camel-jsonapi/src/main/docs/jsonApi-dataformat.adoc +++ b/components/camel-jsonapi/src/main/docs/jsonApi-dataformat.adoc @@ -18,12 +18,11 @@ include::partial$dataformat-options.adoc[] == Dependencies -To use JsonAPI in your camel routes you need to add the dependency +To use JsonAPI in your Camel routes, you need to add the dependency on *camel-jsonapi* which implements this data format. -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] ---- From ec9ec0ac074ecbc7865f0788ad3d9a84fc4ee19d Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:34:10 +0100 Subject: [PATCH 07/11] CAMEL-20410: documentation fixes for camel-jsonata - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../camel-jsonata/src/main/docs/jsonata-component.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/components/camel-jsonata/src/main/docs/jsonata-component.adoc b/components/camel-jsonata/src/main/docs/jsonata-component.adoc index 9982019a72597..7ba453635d94b 100644 --- a/components/camel-jsonata/src/main/docs/jsonata-component.adoc +++ b/components/camel-jsonata/src/main/docs/jsonata-component.adoc @@ -40,7 +40,7 @@ jsonata:specName[?options] Where *specName* is the classpath-local URI of the specification to invoke; or the complete URL of the remote specification -(eg: \file://folder/myfile.vm). +(e.g.: `\file://folder/myfile.vm`). // component-configure options: START @@ -58,7 +58,7 @@ include::partial$component-endpoint-options.adoc[] == Samples -For example you could use something like +For example, you could use something like: [source,java] -------------------------------------- @@ -66,7 +66,7 @@ from("activemq:My.Queue"). to("jsonata:com/acme/MyResponse.json"); -------------------------------------- -And a file based resource: +And a file-based resource: [source,java] --------------------------------------------------------------- From 13783a932a7c719dd6fe726e31664f923d923139 Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:35:55 +0100 Subject: [PATCH 08/11] CAMEL-20410: documentation fixes for camel-jsonb - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../camel-jsonb/src/main/docs/jsonb-dataformat.adoc | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/components/camel-jsonb/src/main/docs/jsonb-dataformat.adoc b/components/camel-jsonb/src/main/docs/jsonb-dataformat.adoc index 9b43f897e7888..bd991b25f0356 100644 --- a/components/camel-jsonb/src/main/docs/jsonb-dataformat.adoc +++ b/components/camel-jsonb/src/main/docs/jsonb-dataformat.adoc @@ -11,7 +11,7 @@ *Since Camel {since}* -JSON-B is a Data Format which uses the standard (javax) JSON-B library. +JSON-B is a Data Format that uses the standard (javax) JSON-B library. [source,java] ------------------------------- @@ -31,12 +31,11 @@ include::partial$dataformat-options.adoc[] == Dependencies -To use JSON-B in your camel routes you need to add the dependency -on *camel-jsonb* which implements this data format. +To use JSON-B in your Camel routes, you need to add the dependency +on *camel-jsonb* that implements this data format. -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] ---------------------------------------------------------- @@ -50,7 +49,7 @@ the download page for the latest versions). You have to add a dependency on the *implementation* of a jsonb specification. -If you want to add the Johnzon implementation and you are using maven, just add following to your pom.xml +If you want to add the Johnzon implementation, and you are using maven, add following to your `pom.xml`: [source,xml] ---------------------------------------------------------- From cd6b1b1fcc10e4b9e2dae5d60e0837772648f4b5 Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:39:53 +0100 Subject: [PATCH 09/11] CAMEL-20410: documentation fixes for camel-jsonpath - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../src/main/docs/jsonpath-language.adoc | 68 +++++++++++++------ 1 file changed, 48 insertions(+), 20 deletions(-) diff --git a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc index b73e2177370b0..d93c48c8603aa 100644 --- a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc +++ b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc @@ -25,8 +25,13 @@ include::partial$language-options.adoc[] == Examples For example, you can use JSONPath 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. +[tabs] +==== + +Java:: ++ [source,java] ---- from("queue:books.new") @@ -39,8 +44,8 @@ from("queue:books.new") .to("jms:queue:book.expensive"); ---- -And in XML DSL: - +XML DSL:: ++ [source,xml] ---- @@ -61,10 +66,12 @@ And in XML DSL: ---- +==== + == JSONPath Syntax Using the JSONPath syntax takes some time to learn, even for basic predicates. -So for example to find out all the cheap books you have to do: +So for example, to find out all the cheap books you have to do: [source,text] ---- @@ -124,18 +131,23 @@ Camel JSONPath supports message body using the following types: | InputStream | If none of the above types matches, then Camel will attempt to read the message body as a `java.io.InputStream`. |=== -If a message body is of unsupported type then an exception is thrown by default, however you -can configure JSONPath to suppress exceptions (see below) +If a message body is of unsupported type, then an exception is thrown by default. +However, you can configure JSONPath to suppress exceptions (see below) == Suppressing exceptions By default, jsonpath will throw an exception if the json payload does not have a valid path accordingly to the configured jsonpath expression. In -some use-cases you may want to ignore this in case the json payload +some use-cases, you may want to ignore this in case the json payload contains optional data. Therefore, you can set the option `suppressExceptions` to `true` to ignore this as shown: +[tabs] +==== + +Java:: ++ [source,java] ---- from("direct:start") @@ -147,8 +159,8 @@ from("direct:start") .to("mock:other"); ---- -And in XML DSL: - +XML DSL:: ++ [source,xml] ---- @@ -165,6 +177,8 @@ And in XML DSL: ---- +==== + This option is also available on the `@JsonPath` annotation. == Inline Simple expressions @@ -174,6 +188,11 @@ in the JSONPath expression using the simple syntax `$\{xxx}`. An example is shown below: +[tabs] +==== + +Java:: ++ [source,java] ---- from("direct:start") @@ -186,8 +205,8 @@ from("direct:start") .to("mock:expensive"); ---- -And in XML DSL: - +XML DSL:: ++ [source,xml] ---- @@ -208,20 +227,29 @@ And in XML DSL: ---- +==== + You can turn off support for inlined Simple expression by setting the option `allowSimple` to `false` as shown: +[tabs] +==== + +Java:: ++ [source,java] ---- .when().jsonpath("$.store.book[?(@.price < 10)]", false, false) ---- -And in XML DSL: - +XML DSL:: ++ [source,xml] ---- $.store.book[?(@.price < 10)] ---- +==== + == JSONPath injection You can use xref:manual::bean-integration.adoc[Bean Integration] to invoke a @@ -242,9 +270,9 @@ public class Foo { == Encoding Detection The encoding of the JSON document is -detected automatically, if the document is encoded in unicode (UTF-8, -UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE ) as specified in RFC-4627. If -the encoding is a non-unicode encoding, you can either make sure that +detected automatically, if the document is encoded in unicode (UTF-8, +UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE) as specified in RFC-4627. +If the encoding is a non-unicode encoding, you can either make sure that you enter the document in String format to JSONPath, or you can specify the encoding in the header `CamelJsonPathJsonEncoding` which is defined as a constant in: `JsonpathConstants.HEADER_JSON_ENCODING`. @@ -284,14 +312,14 @@ from("direct:start") .to("log:book"); ---- -If book array contains only one book, it will be converted into a Book object. +If a book array contains only one book, it will be converted into a Book object. == Using header as input By default, JSONPath uses the message body as the input source. However, you can also use a header as input by specifying the `headerName` option. -For example to count the number of books from a JSON document that +For example, to count the number of books from a JSON document that was stored in a header named `books` you can do: [source,java] @@ -320,10 +348,10 @@ The same example in XML DSL would be: == Transforming a JSon message -For basic JSon transformation where you have a fixed structure you can represent with a combination of using +For basic JSon transformation where you have a fixed structure, you can represent with a combination of using Camel simple and JSonPath language as: -[source] +[source,json] ---- { "company": "${jsonpath($.customer.name)}", From b258828c0108108d49d29b2a410a7b08d71a644d Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:42:04 +0100 Subject: [PATCH 10/11] CAMEL-20410: documentation fixes for camel-jt400 - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- .../camel-jt400/src/main/docs/jt400-component.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/components/camel-jt400/src/main/docs/jt400-component.adoc b/components/camel-jt400/src/main/docs/jt400-component.adoc index 45a7f9104a7fa..9dea6b5d47a9a 100644 --- a/components/camel-jt400/src/main/docs/jt400-component.adoc +++ b/components/camel-jt400/src/main/docs/jt400-component.adoc @@ -79,8 +79,8 @@ When configured as a message queue consumer endpoint, the endpoint will poll a message queue on an IBM i system. For every entry on the queue, a new `Exchange` is sent with the entry's data in the _In_ message's body. The data is always formatted as a `String`. Note that only new messages will -be processed. That is, any existing messages on the queue that have already -been handled by another program will not be processed by this endpoint. +be processed. That is, this endpoint will not process any existing messages +on the queue that have already been handled by another program. For a data queue provider endpoint, the _In_ message body contents will be put on the data queue as either raw bytes or text. @@ -104,8 +104,8 @@ mechanisms. A parameter can be _omitted_ by passing null as the value in its position (the program has to support it). After the program execution, the endpoint returns an `Object[]` in the message body. Depending on _format_, the returned array will be populated with `byte[]` or `String` -objects representing the values as they were returned by the program. Input -only parameters will contain the same data as the beginning of the invocation. +objects representing the values as they were returned by the program. +Input-only parameters will contain the same data as the beginning of the invocation. This endpoint does not implement a provider endpoint! // component headers: START @@ -134,9 +134,9 @@ public class Jt400RouteBuilder extends RouteBuilder { === Program call examples In the snippet below, the data Exchange sent to the direct:work endpoint -will contain three string that will be used as the arguments for the +will contain three strings that will be used as the arguments for the program “compute” in the library “assets”. This program will write the -output values in the 2nd and 3rd parameters. All the parameters will be +output values in the second and third parameters. All the parameters will be sent to the direct:play endpoint. [source,java] From 8028c0b72cd93f2127ba859731ea02f85e8d6c23 Mon Sep 17 00:00:00 2001 From: Otavio Rodolfo Piske Date: Wed, 21 Feb 2024 11:43:31 +0100 Subject: [PATCH 11/11] CAMEL-20410: documentation fixes for camel-jte - Fixed samples - Fixed grammar and typos - Fixed punctuation - Added and/or fixed links - Converted to use tabs --- components/camel-jte/src/main/docs/jte-component.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/components/camel-jte/src/main/docs/jte-component.adoc b/components/camel-jte/src/main/docs/jte-component.adoc index e5178e756d1ca..f0d8ddccfd8ec 100644 --- a/components/camel-jte/src/main/docs/jte-component.adoc +++ b/components/camel-jte/src/main/docs/jte-component.adoc @@ -41,7 +41,7 @@ jte:templateName[?options] --------------------------------- Where *templateName* is the classpath-local URI of the template to -invoke; or the complete URL of the remote template (eg: +invoke; or the complete URL of the remote template (e.g.: `\file://folder/myfile.jte`). @@ -82,7 +82,7 @@ with the following information: |======================================================================= -You can setup your custom JTE data model in the +You can set up your custom JTE data model in the message header with the key "*CamelJteDataModel*" just like this @@ -90,7 +90,7 @@ message header with the key "*CamelJteDataModel*" just like this 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 @@ -99,7 +99,7 @@ include::partial$component-endpoint-headers.adoc[] == Samples -For example you could use something like: +For example, you could use something like: [source,java] ------------------------------------------- @@ -107,7 +107,7 @@ from("rest:get:item/{id}"). to("jte:com/acme/response.jte"); ------------------------------------------- -To use a JTE template to formulate a response to the REST get call. +To use a JTE template to formulate a response to the REST get call: [source,java] ----