Robust-oneway pattern string encoding/decoding does not work

[GoogleCodeExporter]

Encoding in output file is wrong for input files with ISO-8859-1 encoding.

For example: output is "�" (i.e. the code for parse/encoding error) for 
the inbound umlaut "Ö" character.

It seems like the encoding conversion in the process-stage:

  <byte-array-to-string-transformer encoding="ISO-8859-1" doc:name="Byte Array to String"/>

  <custom-transformer doc:name="Transform message" class="org.sample.filetoftp.flow1.process.Flow1Transformer"/>

  <string-to-byte-array-transformer encoding="ISO-8859-1" doc:name="String to Byte Array"/>

doesn't work. Probably uses default UTF-8 instead of ISO-8859-1.

Original issue reported on code.google.com by hakan.d...@gmail.com on 4 Nov 2013 at 9:22

• Blocking: #343

[GoogleCodeExporter]

Original comment by hakan.d...@gmail.com on 4 Nov 2013 at 9:22

• Now blocking: #343

[GoogleCodeExporter]

Misconception, from transformer ref docs: "String encoding used for transformer 
output."
I.e. the encoding must be set before the transformer in the flow to be used in 
the transformer.

Original comment by hakan.d...@gmail.com on 16 Dec 2013 at 10:12

[GoogleCodeExporter]

This issue was closed by revision r2112.

Original comment by hakan.d...@gmail.com on 24 Jan 2014 at 4:53

• Changed state: Fixed

[GoogleCodeExporter]

Removed the <byte-array-to-string-transformer ... transformers and let the
custom transformer have byte[] as in/out type - and handle encoding explicitly
in the transformer.
This is for example consistent with how an XSLT transformation would work.

Original comment by hakan.d...@gmail.com on 24 Jan 2014 at 4:54