This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1fbf7d9f452a6c2ace07f13d94ab89acbcea374a
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Mar 24 18:43:30 2021 +0100
CAMEL-16393: Add WARN to json-path documentation about concat function has
a bug and does not work.
---
.../org/apache/camel/catalog/docs/jsonpath-language.adoc | 9 ++++++---
components/camel-jsonpath/src/main/docs/jsonpath-language.adoc | 9 ++++++---
docs/components/modules/languages/pages/jsonpath-language.adoc | 9 ++++++---
3 files changed, 18 insertions(+), 9 deletions(-)
diff --git
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jsonpath-language.adoc
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jsonpath-language.adoc
index 6744e62..77d521d 100644
---
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jsonpath-language.adoc
+++
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/jsonpath-language.adoc
@@ -80,9 +80,12 @@ follows
== Syntax
-See the https://code.google.com/p/json-path/[JSonPath] project page for
+See the https://github.com/json-path/JsonPath[JSonPath] project page for
further examples.
+WARNING: The `concat` function in
https://github.com/json-path/JsonPath[JSonPath] has a
https://issues.apache.org/jira/browse/CAMEL-16393[bug] and does not work. Do
not use this function.
+You can instead store information in Camel exchange properties or headers and
then concat those together afterwards using Camel's simple language.
+
== Easy Syntax
*Since Camel 2.19*
@@ -134,8 +137,8 @@ Camel JSonPath supports message body using the following
types:
| List | Message bodies as `java.util.List` types
| POJO | *Optional* If Jackson is on the classpath, then camel-jsonpath
is able to use Jackson to read the message body as POJO and convert to
`java.util.Map`
- which is supported by JSonPath. For example you can add `camel-jackson` as
dependency to include Jackson.
-| InputStream | If none of the above types matches, then Camel will attempt to
read the message body as an `java.io.InputStream`.
+ which is supported by JSonPath. For example, you can add `camel-jackson` as
dependency to include Jackson.
+| 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
diff --git a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
index 6744e62..77d521d 100644
--- a/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
+++ b/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
@@ -80,9 +80,12 @@ follows
== Syntax
-See the https://code.google.com/p/json-path/[JSonPath] project page for
+See the https://github.com/json-path/JsonPath[JSonPath] project page for
further examples.
+WARNING: The `concat` function in
https://github.com/json-path/JsonPath[JSonPath] has a
https://issues.apache.org/jira/browse/CAMEL-16393[bug] and does not work. Do
not use this function.
+You can instead store information in Camel exchange properties or headers and
then concat those together afterwards using Camel's simple language.
+
== Easy Syntax
*Since Camel 2.19*
@@ -134,8 +137,8 @@ Camel JSonPath supports message body using the following
types:
| List | Message bodies as `java.util.List` types
| POJO | *Optional* If Jackson is on the classpath, then camel-jsonpath
is able to use Jackson to read the message body as POJO and convert to
`java.util.Map`
- which is supported by JSonPath. For example you can add `camel-jackson` as
dependency to include Jackson.
-| InputStream | If none of the above types matches, then Camel will attempt to
read the message body as an `java.io.InputStream`.
+ which is supported by JSonPath. For example, you can add `camel-jackson` as
dependency to include Jackson.
+| 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
diff --git a/docs/components/modules/languages/pages/jsonpath-language.adoc
b/docs/components/modules/languages/pages/jsonpath-language.adoc
index 0c26e35..f2f0f17 100644
--- a/docs/components/modules/languages/pages/jsonpath-language.adoc
+++ b/docs/components/modules/languages/pages/jsonpath-language.adoc
@@ -82,9 +82,12 @@ follows
== Syntax
-See the https://code.google.com/p/json-path/[JSonPath] project page for
+See the https://github.com/json-path/JsonPath[JSonPath] project page for
further examples.
+WARNING: The `concat` function in
https://github.com/json-path/JsonPath[JSonPath] has a
https://issues.apache.org/jira/browse/CAMEL-16393[bug] and does not work. Do
not use this function.
+You can instead store information in Camel exchange properties or headers and
then concat those together afterwards using Camel's simple language.
+
== Easy Syntax
*Since Camel 2.19*
@@ -136,8 +139,8 @@ Camel JSonPath supports message body using the following
types:
| List | Message bodies as `java.util.List` types
| POJO | *Optional* If Jackson is on the classpath, then camel-jsonpath
is able to use Jackson to read the message body as POJO and convert to
`java.util.Map`
- which is supported by JSonPath. For example you can add `camel-jackson` as
dependency to include Jackson.
-| InputStream | If none of the above types matches, then Camel will attempt to
read the message body as an `java.io.InputStream`.
+ which is supported by JSonPath. For example, you can add `camel-jackson` as
dependency to include Jackson.
+| 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
