Repository: camel Updated Branches: refs/heads/master ff5ce55f9 -> 8785ff75b
CAMEL-10908 Fixed adoc Project: http://git-wip-us.apache.org/repos/asf/camel/repo Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/8785ff75 Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/8785ff75 Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/8785ff75 Branch: refs/heads/master Commit: 8785ff75b0dabcace32d3bdf9ff9004ea50727a2 Parents: ff5ce55 Author: Tomohisa Igarashi <tm.igara...@gmail.com> Authored: Thu Mar 2 11:42:06 2017 +0900 Committer: Andrea Cosentino <anco...@gmail.com> Committed: Thu Mar 2 09:07:12 2017 +0100 ---------------------------------------------------------------------- camel-core/src/main/docs/transformer.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/camel/blob/8785ff75/camel-core/src/main/docs/transformer.adoc ---------------------------------------------------------------------- diff --git a/camel-core/src/main/docs/transformer.adoc b/camel-core/src/main/docs/transformer.adoc index 598f9c2..ee03a70 100644 --- a/camel-core/src/main/docs/transformer.adoc +++ b/camel-core/src/main/docs/transformer.adoc @@ -7,13 +7,13 @@ Transformer Transformer performs declarative transformation of the message according to the declared `Input Type` and/or `Output Type` on a route definition which declares the expected message type. -There are two Exchange property indicates current message type, `Exchange.INPUT_TYPE` -holds input message type and `Exchange.OUTPUT_TYPE` holds output message type. If the -input type and/or output type declared by `Input Type` and/or `Output Type` in the route -definition, and it is different from those properties at runtime, camel internal processor +The default camel Message implements `DataTypeAware`, which allows to hold the message type +represented by `DataType`. +If the input type and/or output type is declared by `Input Type` and/or `Output Type` in the route +definition, and it is different from actual message type at runtime, camel internal processor looks for a Transformer which transforms from the current message type to the expected message -type and apply. Once transform succeed or message is already in expected type, then -`Exchange.INPUT_TYPE` or `Exchange.OUTPUT_TYPE` is updated. +type and apply. Once transform succeed or message is already in expected type, then the message + data type is updated.
