[
https://issues.apache.org/activemq/browse/SM-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41919#action_41919
]
Guillaume Nodet commented on SM-1238:
-------------------------------------
The problem is that if we forward all the headers / properties from endpoint to
endpoint, this will certainly cause problems or unexpected behavior. For
example the HTTP headers from the original requests would be automatically set
as HTTP headers for another web service invocation. And the same would be true
for HTTP headers on the response. For JMS, this could be quite a problem too,
as some JMS headers have very specific meanings. So I think the question is
not so easy to solve. We need to be able to handle most of the use cases, but
also have a default behavior that works well too.
> 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.
