[
https://issues.apache.org/activemq/browse/SM-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41902#action_41902
]
Ron Gavlin commented on SM-1238:
--------------------------------
Hi Guillaume,
The reason I need this support is because transformer components such as
servicemix-http BC provider, CXF-SE, and others do not appear to copy all the
properties from the input message to the output message if they don't exist
yet. Other transformer components, such as servicemix-saxon, appear to copy
properties by default and provide the option to disable this behavior if
desired. If I could be assured that all transformer components assumed
responsibility for copying the properties from the input message to the output
message, then I would not need the Pipeline to do this work.
In general, should components that support an IN-OUT MEP at a minimum, if not
by default, copy all properties from the input message to the output message if
they don't exist? Should I consider it a bug if the specific component does not
either copy the properties by default or at least provide a configurable to let
me do it?
Thanks,
- Ron
> EIP Pipeline should propagate message properties across asynchronous exchanges
> ------------------------------------------------------------------------------
>
> Key: SM-1238
> URL: https://issues.apache.org/activemq/browse/SM-1238
> Project: ServiceMix
> Issue Type: New Feature
> Components: servicemix-eip
> Affects Versions: 3.2.1
> Reporter: Ron Gavlin
> Attachments: Pipeline.java.patch
>
>
> EIP Pipeline output properties should be the same as input properties except
> where modified by the transform in asynchronous exchanges.
> Also, StreamSource faults should be localized before returning to the
> exchange.
> I hope to submit a patch for this issue shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
