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 a261432 CAMEL-14192: regen docs
a261432 is described below
commit a261432514d24194f8b30943dfa55713b721d2d9
Author: Omar Al-Safi <[email protected]>
AuthorDate: Tue Nov 19 16:35:45 2019 +0100
CAMEL-14192: regen docs
---
docs/components/modules/ROOT/pages/protobuf-dataformat.adoc | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/docs/components/modules/ROOT/pages/protobuf-dataformat.adoc
b/docs/components/modules/ROOT/pages/protobuf-dataformat.adoc
index 682d233..066e5c1 100644
--- a/docs/components/modules/ROOT/pages/protobuf-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/protobuf-dataformat.adoc
@@ -87,6 +87,10 @@ from("direct:marshal")
This dataformat supports marshaling input data either as protobuf `Message`
type or `Map` data type. In case of input data as `Map` type, first it will try
to retrieve the data as `Map` using built-in type converters, if it fails to
do so, it will fall back to retrieve it as proto `Message`.
+== Output data type
+As mentioned above, you can define the content type format to choose from JSON
or native to serialize/deserialize data from/to. In addition, you can also
obtain the data as `Map` and let this component to do the heavy lifting to
parse the
+data from proto `Message` to `Map`, you will just need to set the
`contentTypeFormat` to *native* and explicitly define the data type `Map` when
you obtain body of the exchange, e.g:
`exchange.getMessage().getBody(Map.class)`.
+
== Protobuf overview
This quick overview of how to use Protobuf. For more detail see the
