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 e9dcd3afe4712425b658a3bdd7106b53221eb7dc
Author: Otavio R. Piske <angusyo...@gmail.com>
AuthorDate: Sun Feb 25 14:54:00 2024 +0100
CAMEL-20459: minor documentation tweaks for the messaging mapper EIP.
Signed-off-by: Otavio R. Piske <angusyo...@gmail.com>
---
.../src/main/docs/modules/eips/pages/messaging-mapper.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
index 9319dc98dd4..fbc792c17dc 100644
---
a/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
+++
b/core/camel-core-engine/src/main/docs/modules/eips/pages/messaging-mapper.adoc
@@ -9,15 +9,15 @@ How do you move data between domain objects and the messaging
infrastructure whi
image::eip/MessagingMapperClassDiagram.gif[image]
Create a separate Messaging Mapper that contains the mapping logic between the
messaging infrastructure and the domain objects.
-Neither the objects nor the infrastructure have knowledge of the Messaging
Mapper's existence.
+Neither the objects nor the infrastructure has knowledge of the Messaging
Mapper's existence.
The Messaging Mapper accesses one or more domain objects and converts them
into a message as required by the messaging channel.
It also performs the opposite function, creating or updating domain objects
based on incoming messages.
Since the Messaging Mapper is implemented as a separate class that references
the domain object(s)
and the messaging layer, neither layer is aware of the other. The layers don't
even know about the Messaging Mapper.
-With Camel this pattern is often implemented directly via Camel components
that provides
-xref:manual::type-converter.adoc[Type Converter]'s from the messaging
infrastructure to common Java types or
+With Camel, this pattern is often implemented directly via Camel components
that provide
+xref:manual::type-converter.adoc[Type Converters] from the messaging
infrastructure to common Java types or
Java Objects representing the data model of the component in question.
Combining this with the
xref:message-translator.adoc[Message Translator] to have the Messaging Mapper
EIP pattern.
