[camel] branch main updated: CAMEL-18576: camel-base - Move doc about escape a placeholder

[nf...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

nfilotto pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 9537268cc08 CAMEL-18576: camel-base - Move doc about escape a placeholder
9537268cc08 is described below

commit 9537268cc083914b68476a16e065dfa3f8b9cead
Author: Nicolas Filotto <nf...@talend.com>
AuthorDate: Thu Oct 13 09:09:51 2022 +0200

    CAMEL-18576: camel-base - Move doc about escape a placeholder
---
 core/camel-base/src/main/docs/properties-component.adoc           | 8 --------
 .../user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc | 8 ++++++++
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/core/camel-base/src/main/docs/properties-component.adoc b/core/camel-base/src/main/docs/properties-component.adoc
index 186be6a4096..ba6c6397793 100644
--- a/core/camel-base/src/main/docs/properties-component.adoc
+++ b/core/camel-base/src/main/docs/properties-component.adoc
@@ -119,14 +119,6 @@ For fine grained configuration of the location, then this can be done as follows
 </camelContext>
 ----
 
-=== Escape a placeholder
-
-The component allows to refer to the value of a property thanks to placeholders of type `{{property-name}}` but sometimes it can be problematic if the double curly braces are used by a third party library.
-
-To work around that it is possible to escape the double curly braces with a backslash character like for example `\{{ property-name \}}`. This way, it won't be interpreted as a placeholder to resolve and will be resolved as `{{property-name}}`.
-
-If for some reason, the backslash character before the double curly braces must not be interpreted as an escape character, it is possible to add another backslash in front of it to escape it, it will then be seen as a backslash.
-
 == Options
 
 The component supports the following options, which are listed below.
diff --git a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
index d7ec74932a5..ddb0ad3a693 100644
--- a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
+++ b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
@@ -186,6 +186,14 @@ And the route in XML:
 </route>
 ----
 
+=== Escape a property placeholder
+
+The property placeholder can be problematic if the double curly brackets are used by a third party library like for example a query in ElasticSearch of type `{"query":{"match_all":{}}}`.
+
+To work around that it is possible to escape the double curly brackets with a backslash character like for example `\{{ property-name \}}`. This way, it won't be interpreted as a property placeholder to resolve and will be resolved as `{{property-name}}`.
+
+If for some reason, the backslash character before the double curly brackets must not be interpreted as an escape character, it is possible to add another backslash in front of it to escape it, it will then be seen as a backslash.
+
 === Using property placeholders multiple times
 
 You can of couse also use placeholders several times: