[SM-1831] Messages with StaxSource content are not handled well when running in non-DEBUG mode

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.3, 3.3
• Fix Version/s: servicemix-utils-1.5.0
• Component/s: servicemix-utils
• Assignee: Jean-Baptiste Onofré
• Reporter: Ron Gavlin
• Created: 26/Mar/09 08:59
• Updated: 08/Jul/11 16:24
• Resolved: 08/Jul/11 16:24

Description

In order to fully support StaxSource content across the platform, the following changes should be made:

1. Rollup/merge the functionality in class org.apache.servicemix.jbi.jaxp.StaxSourceTransformer into class SourceTransformer. In order to maintain backwards compatibility, an empty org.apache.servicemix.jbi.jaxp.StaxSourceTransformer class should remain

2. Rollup/merge the functionality in class org.apache.servicemix.soap.util.stax.StaxSource into class org.apache.servicemix.jbi.jaxp.StaxSource. In order to maintain backwards compatibility, an empty org.apache.servicemix.soap.util.stax.StaxSource class should remain that extends org.apache.servicemix.jbi.jaxp.StaxSource.

Without this fix, flows that start with the new smx-jms consumer endpoints and require re-readable content have problems.

Please backport this change to the 3.2.x branch.