[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48569#action_48569
]
Ron Gavlin commented on SM-1667:
--------------------------------
Hi Gianfranco,
Although not in the spec, I do believe section 2.5.5 of the "JBI Components
Theory" document
https://open-esb.dev.java.net/public/pdf/JBI-Components-Theory.pdf validates
the existing of an ERROR status for every MEP, including "in-only". While you
could make the argument that the in-only MEP should be fire-and-forget and that
the robust-in-only MEP be stateful, I think there is much value in handling
errors consistently for sync/async uses as well as for all MEPs. JBI is already
complex. Handling errors differently for sync/async and for different MEPs
would only make the situation worse IMHO.
/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.
