[
https://issues.apache.org/activemq/browse/SM-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41921#action_41921
]
Ron Gavlin commented on SM-1238:
--------------------------------
Guillaume,
Based on your comments, it sounds like the use case in which a Pipeline uses an
IN-OUT HTTP or JMS BC provider as its transformer, maybe the right mechanism
for propagating the properties to the target is to do so via this new boolean
property on the Pipeline. OTOH, if the Pipeline were to use a transformer that
took responsibility to copy the properties itself, the new Pipeline boolean
property could be set accordingly to avoid the overhead of copying the
properties. So, the process integrator simply needs to know what to expect from
the transformer it is using with the Pipeline in order to set the boolean
correctly. I agree the default Pipeline behavior should be to refrain from
copying the properties.
Bruce, I don't understand the relevance of your proposed storeAllProperties
here or how a Memory vs. JDBC Store is significant.
- 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.
