This is an automated email from the ASF dual-hosted git repository.
orpiske pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 1fca7f53b76c98f61559c8b4679a4a47a5e101b9
Author: Otavio R. Piske <angusyo...@gmail.com>
AuthorDate: Sat Feb 24 09:44:33 2024 +0100
CAMEL-20459: documentation fixes for the bean EIP.
Signed-off-by: Otavio R. Piske <angusyo...@gmail.com>
---
.../src/main/docs/modules/eips/pages/bean-eip.adoc | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/bean-eip.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/bean-eip.adoc
index be27c309b41..023c6555204 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/bean-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/bean-eip.adoc
@@ -19,7 +19,7 @@ which also is used for invoking beans, but in the form as a
Camel component.
bean:beanID[?options]
----
-Where *beanID* can be any string which is used to look up the bean in
+Where *beanID* can be any string used to look up the bean in
the xref:manual::registry.adoc[Registry].
== EIP options
@@ -37,7 +37,7 @@ include::partial$eip-exchangeProperties.adoc[]
=== Bean scope
When using `singleton` scope (default) the bean is created or looked up only
once and reused for the lifetime of the endpoint.
-The bean should be thread-safe in case concurrent threads is calling the bean
at the same time.
+The bean should be thread-safe in case concurrent threads are calling the bean
at the same time.
When using `request` scope the bean is created or looked up once per request
(exchange). This can be used if you want to store state on a bean
while processing a request, and you want to call the same bean instance
multiple times while processing the request.
@@ -108,8 +108,8 @@ YAML::
----
====
-Instead of passing name of the reference to the bean (so that Camel will
-lookup for it in the registry), you can provide the bean:
+Instead of passing the name of the reference to the bean (so that Camel will
+look up for it in the registry), you can provide the bean:
[tabs]
====
@@ -117,13 +117,13 @@ Java::
+
[source,java]
----
-// Send message to the given bean instance.
+// Send a message to the given bean instance.
from("direct:foo").bean(new ExampleBean());
// Explicit selection of bean method to be invoked.
from("direct:bar").bean(new ExampleBean(), "myMethod");
-// Camel will create a singleton instance of the bean, and reuse the instance
for following calls (see scope)
+// Camel will create a singleton instance of the bean, and reuse the instance
for the following calls (see scope)
from("direct:cheese").bean(ExampleBean.class);
----
@@ -175,6 +175,5 @@ YAML::
How bean methods to be invoked are chosen (if they are not specified
explicitly through the *method* parameter) and how parameter values are
constructed from the xref:message.adoc[Message] are all defined by the
-xref:manual::bean-binding.adoc[Bean Binding] mechanism which is used throughout
-all the various xref:manual::bean-integration.adoc[Bean Integration]
-mechanisms in Camel.
+xref:manual::bean-binding.adoc[Bean Binding] mechanism.
+This is used throughout all the various
xref:manual::bean-integration.adoc[Bean Integration] mechanisms in Camel.
