[
https://issues.apache.org/activemq/browse/SM-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Gavlin updated SM-1831:
---------------------------
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.
was:
There are two almost identical StaxSource classes in packages
org.apache.servicemix.soap.util.stax and org.apache.servicemix.jbi.jaxp.
These versions should be merged and the class in package
org.apache.servicemix.soap.util.stax be made to simply extend the class in
package org.apache.servicemix.jbi.jaxp.
This will allow the org.apache.servicemix.jbi.jaxp.StaxSourceTransformer to
transform instances of either class.
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.
Summary: Messages with StaxSource content are not handled well when
running in non-DEBUG mode (was: Merge StaxSource classes in packages
org.apache.servicemix.soap.util.stax and org.apache.servicemix.jbi.jaxp and
make soap.util.stax version extend jbi.jaxp version)
> Messages with StaxSource content are not handled well when running in
> non-DEBUG mode
> ------------------------------------------------------------------------------------
>
> Key: SM-1831
> URL: https://issues.apache.org/activemq/browse/SM-1831
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-utils
> Affects Versions: 3.2.3, 3.3
> Reporter: Ron Gavlin
>
> 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.
-
You can reply to this email to add a comment to the issue online.
