[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48580#action_48580
]
Andrea Zoppello commented on SM-1667:
-------------------------------------
Hi Guillaume,
I think that what you are saying is right and i find ( despite is on the
specification or not ) that to have the error status
is quite useful.
But i don't agree that if InOnly MEP terminate with an ERROR status it should
propagated back.
I agree totally with Gianfranco this should be done only when we're working in
sync mode, otherwise it's better not
to propagate the error back and use feature like restart from the failure
point, that we've just implemeted.
Do you agree with this??
Andrea
> TransformBeanSupport does not correctly report errors for in-only exchanges
> ---------------------------------------------------------------------------
>
> Key: SM-1667
> URL: https://issues.apache.org/activemq/browse/SM-1667
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-bean
> Affects Versions: servicemix-bean-2008.01
> Reporter: Ron Gavlin
> Assignee: Guillaume Nodet
> Priority: Critical
> Fix For: servicemix-bean-2008.02, 3.2.4
>
> Attachments: sm-1667-inout-regression.patch
>
>
> The smx-bean TransformBeanSupport class does not correctly report errors for
> in-only exchanges. If the target exchange status is ERROR, the source
> exchange status is still returned as DONE. This should be fixed for both sync
> and async use cases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
