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

davsclaus 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 949b763  fix some attribute problems (#6050)
949b763 is described below

commit 949b76328d311ad821e80d8cbc8787a833057b3f
Author: djencks <djen...@apache.org>
AuthorDate: Fri Sep 3 22:35:24 2021 -0700

    fix some attribute problems (#6050)
---
 .../src/main/docs/modules/languages/pages/simple-language.adoc        | 2 +-
 docs/user-manual/modules/ROOT/pages/route-template.adoc               | 4 ++--
 docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc    | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git 
a/core/camel-core-languages/src/main/docs/modules/languages/pages/simple-language.adoc
 
b/core/camel-core-languages/src/main/docs/modules/languages/pages/simple-language.adoc
index 01e4dc3..d811592 100644
--- 
a/core/camel-core-languages/src/main/docs/modules/languages/pages/simple-language.adoc
+++ 
b/core/camel-core-languages/src/main/docs/modules/languages/pages/simple-language.adoc
@@ -32,7 +32,7 @@ language uses OGNL expressions, such as calling a method 
named `myMethod` on the
 At runtime the simple language will then us its built-in OGNL support which 
requires the `camel-bean` component.
 ====
 
-The simple language uses `${body}` placeholders for complex expressions or 
functions.
+The simple language uses `$\{body}` placeholders for complex expressions or 
functions.
 
 [NOTE]
 ====
diff --git a/docs/user-manual/modules/ROOT/pages/route-template.adoc 
b/docs/user-manual/modules/ROOT/pages/route-template.adoc
index 4668ce3..bce8397 100644
--- a/docs/user-manual/modules/ROOT/pages/route-template.adoc
+++ b/docs/user-manual/modules/ROOT/pages/route-template.adoc
@@ -147,7 +147,7 @@ This ensures that the code creating the bean is executed 
later ( when Camel is c
 then the code must be specified as a _supplier_. Because we want during 
creation of the bean access to template parameters,
 we use a Camel `BeanSupplier` which gives access to `RouteTemplateContext` 
that is the _rtc_ variable in the code above.
 
-*Important:* the local bean with id `myClient` *must* be referred to using 
Camel's property placeholder syntax, eg `{{myClient}}`
+*Important:* the local bean with id `myClient` *must* be referred to using 
Camel's property placeholder syntax, eg `{\{myClient}}`
 in the route template, as shown above with the _to_ endpoint. This is because 
the local
 bean must be made unique and Camel will internally re-assign the bean id to 
use an unique id instead of `myClient`. And this is done with the help
 of the property placeholder functionality.
@@ -175,7 +175,7 @@ Suppose the route template below is defined in XML:
 </camelContext>
 ----
 
-The template has no bean bindings for `#{{myClient}}` which would be required 
for creating the template.
+The template has no bean bindings for `#{\{myClient}}` which would be required 
for creating the template.
 
 When creating routes form the template via `TemplatedRouteBuilder` then you 
can provide the bean binding
 if you desire the bean to be local scoped (not shared with others):
diff --git a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc 
b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
index 4310936..1d70f6d 100644
--- a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
+++ b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
@@ -103,7 +103,7 @@ We can do this be negating the `autoStartup` in the JMS 
route, by using `!integr
 
 == Using property placeholders
 
-When using property placeholders in the endpoint xref:uris.adoc[URIs] you 
should use this with the syntax `{{key}}` as shown in this example:
+When using property placeholders in the endpoint xref:uris.adoc[URIs] you 
should use this with the syntax `{\{key}}` as shown in this example:
 
 [source,properties]
 ----
@@ -393,7 +393,7 @@ tag as shown below:
 
 Notice how the hello bean is using pure Spring property placeholders using
 the `${}` notation. And in the Camel routes we use the Camel
-placeholder notation with `{{key}}`.
+placeholder notation with `{\{key}}`.
 
 == Using property placeholder functions
 

Reply via email to