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 73a7c5e typo
73a7c5e is described below
commit 73a7c5e843aee06e1b88f188082273c5380f9bf1
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Thu Dec 16 09:45:07 2021 +0100
typo
---
docs/user-manual/modules/ROOT/pages/route-template.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/user-manual/modules/ROOT/pages/route-template.adoc
b/docs/user-manual/modules/ROOT/pages/route-template.adoc
index 2a73074..095e493 100644
--- a/docs/user-manual/modules/ROOT/pages/route-template.adoc
+++ b/docs/user-manual/modules/ROOT/pages/route-template.adoc
@@ -450,7 +450,7 @@ then you can create the local bean using Java lambda style
as previously documen
==== Configuring the type of the created bean
When using scripting languages to create the local bean, then Camel would not
know what type (fully qualified class name)
-then created bean is. The type is therefore unassigned (is set as
`java.lang.Object`) which is a slight limitation.
+the created bean is. The type is therefore unassigned (is set as
`java.lang.Object`) which is a slight limitation.
If you use dependency injection by type, or have the need for looking up the
local bean from the Camel `Registry` via its type,
then you must provide this information in the route template with `beanType`
as shown:
