[JBoss JIRA] Created: (JBESB-3649) SmooksAction / ContentBasedRouter fails with input data containing a byte order mark (BOM)
11:17 p.m.
SmooksAction / ContentBasedRouter fails with input data containing a byte order mark
(BOM)
------------------------------------------------------------------------------------------
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
5:02 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3649) Add a Byte Order Mark (BOM) filtering action
[
https://issues.jboss.org/browse/JBESB-3649?page=com.atlassian.jira.plugin...
]
Tom Fennelly updated JBESB-3649:
--------------------------------
Summary: Add a Byte Order Mark (BOM) filtering action (was: SmooksAction /
ContentBasedRouter fails with input data containing a byte order mark (BOM))
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
5:04 p.m.
New subject: [JBoss JIRA] Resolved: (JBESB-3649) Add a Byte Order Mark (BOM) filtering action
[
https://issues.jboss.org/browse/JBESB-3649?page=com.atlassian.jira.plugin...
]
Tom Fennelly resolved JBESB-3649.
---------------------------------
Resolution: Done
branches/JBESB_4_10_CP: 37466
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
5:10 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBESB-3649) Add a Byte Order Mark (BOM) filtering action
[
https://issues.jboss.org/browse/JBESB-3649?page=com.atlassian.jira.plugin...
]
Tom Fennelly edited comment on JBESB-3649 at 9/15/11 11:09 AM:
---------------------------------------------------------------
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 (with the
contentEncoding coming from the servlet request), so in that case, you shouldn't need
to specify the "contentEncoding" config on the action config.
was (Author: tfennelly):
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
5:10 p.m.
New subject: [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
4:31 p.m.
New subject: [JBoss JIRA] (JBESB-3649) Add a Byte Order Mark (BOM) filtering action
[
https://issues.jboss.org/browse/JBESB-3649?page=com.atlassian.jira.plugin...
]
Martin Vecera updated JBESB-3649:
---------------------------------
Priority: Blocker (was: Major)
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
Priority: Blocker
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:39 p.m.
New subject: [JBoss JIRA] (JBESB-3649) Add a Byte Order Mark (BOM) filtering action
[
https://issues.jboss.org/browse/JBESB-3649?page=com.atlassian.jira.plugin...
]
Martin Vecera closed JBESB-3649.
--------------------------------
Ok, it is actually verified in ER6.
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
Priority: Blocker
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4615
days inactive
4719
days old
6 comments
4 participants
participants (4)
-
Martin Vecera (Closed) (JIRA) -
Martin Vecera (Updated) (JIRA)
-
Tom Cunningham (JIRA)
-
Tom Fennelly (JIRA)