[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48588#action_48588
]
Andrea Zoppello commented on SM-1667:
-------------------------------------
Hi Guillaume,
I read carefully what you said, and it seems you agree with me.
The scenario you describe make perfect sense, but what you're describing is a
scenario within transaction management
where if i understand well you need to use sendSync ( right or not ??? ).
I've not try directly but if i remember well the only way tomake automatic
transaction work is to use sendSync.
In that case i want to repeat myself it perfect make sense, the exchange must
be propagate back in all the chain.
But let immagine a scenario where i do not want automatic transaction
management, because i want all my exchange will
use send instead of sendSync, handling fault manually ( think for example
compensation handler and error handler in bpel ),
the back propagation of the exchange does not make sense in that case.
Finally my opinion is that:
1) In all scenario where the exchanges are propagated using sendSync and, the
approach provided by Ron is right
2) In all other scenario, where all the InOnly MEP are propagated using send it
does not make sense.
Hope this help.
Thoughts??
> 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.
