[jira] Commented: (SM-1238) EIP Pipeline should propagate message properties across asynchronous exchanges

["Andrea Zoppello (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41730#action_41730 ] 

Andrea Zoppello commented on SM-1238:
-------------------------------------

Hi Guillaume,

I agree with the part about the source.

We've done to handle the specific error
Let me to explain the contetxt,  when we use the pipeline with an  HTTP InOut Transformer  and the webeservice was not availabel we had in the pipeline an HTML Page containing the "PAGE NOT FOUND ERROR", this was causing a problem ( but maybe in previous version of servicemix ) in the old pipeline code.

I need to receck this, but probably is not needed anymore, so not take that part of the patch.

Regarding the property, if there's a better way to get the "my requirement" it's ok for me.

Basically what i need is that the properties that are in in the icnoming of the pipeline will be in the message outcoming from the eip-pipeline once the transformer is called.

If i understand right you say that it's the HTTP InOut ( the pipeline - transformer ) that should care about the copy of the properties... Am I right??


 

> 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.