Known Issues for the File Binding Component

The following are known issues for the File Binding Component:

• The File BC supports encodings in UTF-8 format only; if the encoding is in non-UTF-8 format, the File BC fails to read the input data. However, data of any encoding style (either UTF or non-UTF-8) and binary data can both be forwarded as attachments.

  You can work around the UTF-8 limitation by doing the following:

  • To read non-UTF-8 data, employ a custom encoder upstream of the File BC and convert it to UTF-8 format, which in turn can be provided as input to File BC.

  • To write non-UTF-8 data, route the output from the File BC to a custom encoder and convert it from UTF-8 to the preferred encoding format. For more information, refer to Designing Custom Encoders.

• Issue 1206

  On the Windows operating system, when the File BC transforms XML text to bytes, an additional carriage return is added for each newline character. For example, \r\n is converted to \r\r\n.

• Issue 2025

  When using the File BC in on-demand mode and setting a normalized message property value for an assign activity, if you set the property value in the ReadOut node, it is not used by the application. You need to set the values in the ReadIn node.