[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48531#action_48531
]
Ron Gavlin commented on SM-1667:
--------------------------------
Hi Gianfranco,
I believe the JBI spec requires that message exchange semantics be identical
for both sync and async use cases. The recent changes made to various
components addresses cases where these components were not jbi-compliant when
used asynchronously.
These changes allow appropriate JBI error/fault handling to be introduced
anywhere in the flow for both sync and now async flows. In particular, the
smx-camel errorHandler can now be injected into sync and async flows to provide
detailed error/exception processing. IMO, this is a dramatic improvement over
other work-arounds, such as listening for fault/error exchanges on the nmr and
then attempting to do something smart with them at the SA boundary.
Thoughts?
/Ron
> 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.
