You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by oa...@apache.org on 2020/08/24 14:44:42 UTC

[camel] branch master updated: Add a note to azure eventhubs component docs

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 0e631ce  Add a note to azure eventhubs component docs
0e631ce is described below

commit 0e631ceba9424478960e411aa0fd9e36249cde9c
Author: Omar Al-Safi <om...@gmail.com>
AuthorDate: Mon Aug 24 16:44:27 2020 +0200

    Add a note to azure eventhubs component docs
---
 docs/components/modules/ROOT/pages/azure-eventhubs-component.adoc | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/components/modules/ROOT/pages/azure-eventhubs-component.adoc b/docs/components/modules/ROOT/pages/azure-eventhubs-component.adoc
index f897ae5..e581462 100644
--- a/docs/components/modules/ROOT/pages/azure-eventhubs-component.adoc
+++ b/docs/components/modules/ROOT/pages/azure-eventhubs-component.adoc
@@ -201,8 +201,7 @@ This allows camel route to consume and produce events asynchronously without blo
 
 === Message body type
 The component's producer expects the data in the message body to be in `byte[]`. This allows the user to utilize Camel TypeConverter to marshal/unmarshal data with ease.
-The same goes as well for the component's consumer, it will set the encoded data as `byte[]` in the message body.
-
+The same goes as well for the component's consumer, it will set the encoded data as `byte[]` in the message body. Therefore, Camel will try first to convert the data to `byte[]` using the provided the typeConverters in the Camel context (e.g: `String` to `byte[]`).
 
 === Automatic detection of EventHubProducerAsyncClient client in registry