Replies: 1 comment
-
Disregard, it was an issue with my source transformer parsing XML to JSON. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When do I use
connectorMessage.getRawData()
andconnectorMessage.getEncodedData()
? Also why are there differing strings returned on the source transformer vs the destination transfomer?I understand from the docs -
connectorMessage
: An instance of theImmutableConnectorMessage
Java class; an internal representation of the message and its attributes.From testing, I use
connectorMessage.getRawData()
in the transformer andconnectorMessage.getEncodedData()
in the connector. I don't understand why besides the access to the raw/encoded data at the connector/transformer level. It doesn't follow 'The Message Processing Lifecycle" that I would expect where, the connector would be raw and the transformer would be encoded as quoted below?This is what I have set up on version 4..0.1:
Source connector - DB Reader (Inbound XML, Outbound XML)
Destination connector - File Writer (Inbound XML, Outbound JSON)
Why do these 2 transformers on the source and destination return 2 different strings? I'm thinking Database Reader returns XML string. It gets encoded to the destination?
Source transformer
connectorMessage.getRawData()
returns xml string (regardless if the outbound is XML/RAW)Destination transformer
connectorMessage.getRawData()
returns JSON stringDestination connector
connectorMessage.getEncodedData()
returns JSON stringBeta Was this translation helpful? Give feedback.
All reactions