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

["Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SM-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved SM-1831.
--------------------------------------

    Resolution: Fixed

I made the refactoring in servicemix-utils and updated the dependent projects (components, smx3, ...).

> Messages with StaxSource content are not handled well when running in non-DEBUG mode
> ------------------------------------------------------------------------------------
>
>                 Key: SM-1831
>                 URL: https://issues.apache.org/jira/browse/SM-1831
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-utils
>    Affects Versions: 3.2.3, 3.3
>            Reporter: Ron Gavlin
>            Assignee: Jean-Baptiste Onofré
>             Fix For: servicemix-utils-1.5.0
>
>
> 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. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira