[esb-issues] [JBoss JIRA] Commented: (JBESB-3649) Add a Byte Order Mark (BOM) filtering action
[
https://issues.jboss.org/browse/JBESB-3649?page=com.atlassian.jira.plugin...
]
Tom Fennelly commented on JBESB-3649:
-------------------------------------
So I added org.jboss.soa.esb.actions.converters.BOMFilter
You can configure it in the action pipeline like:
{code}
<action name="action"
class="org.jboss.soa.esb.actions.converters.BOMFilter">
<property name="contentEncoding" value="UTF-8" />
</action>
{code}
The contentEncoding can also be supplied to the action via the Message Properties"
{code}
message.getProperties().setProperty(ActionProcessingConstants.PROPERTY_PAYLOAD_CONTENT_ENCODING,
contentEncoding);
{code}
Where ActionProcessingConstants.PROPERTY_PAYLOAD_CONTENT_ENCODING is
"org.jboss.soa.esb.payload.contentEncoding".
I modified the HttpGatewayServlet to set the contentEncoding on the Message (just like
above), so in that case, you shouldn't need to specify the "contentEncoding"
config on the action config.
Add a Byte Order Mark (BOM) filtering action
--------------------------------------------
Key: JBESB-3649
URL: https://issues.jboss.org/browse/JBESB-3649
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transformation Service
Affects Versions: 4.10
Reporter: Tom Cunningham
Assignee: Tom Fennelly
Fix For: 4.10 CP1
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira