[SOA-3131] SmooksAction / ContentBasedRouter fails with input data containing a byte order mark (BOM) - JBoss Issue Tracker

XML

Word

Printable

Workaround Description:
- Add the message content as byte[] representation instead of a String OR
- Manually remove the BOM from the content before invoking other actions
Release Notes Text:

Hide
https://issues.jboss.org/browse/SOA-3131

ContentBasedRouter failed when input data contained a byte-order mark (BOM). A new ESB BOMFilter action has been added to the enterprise service bus that is able ensure that byte-order marks can now be handled by the software so users will no longer see this failure. The BOMFilter action should be added to the action-chain in order to filter out byte order marks.

Show
https://issues.jboss.org/browse/SOA-3131 ContentBasedRouter failed when input data contained a byte-order mark (BOM). A new ESB BOMFilter action has been added to the enterprise service bus that is able ensure that byte-order marks can now be handled by the software so users will no longer see this failure. The BOMFilter action should be added to the action-chain in order to filter out byte order marks.
Release Notes Docs Status:
Documented as Resolved Issue

Calling a SmooksAction or a ContentBasedRouter with XML data with a preceding BOM, causes it to fail with a 'Content is not allowed in prolog' error.

relates to

JBESB-3649 Add a Byte Order Mark (BOM) filtering action