[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48583#action_48583
]
Ron Gavlin commented on SM-1667:
--------------------------------
Hi Andrea,
What you are describing dramatically changes the semantic of the MEP, based on
whether sync or async is being used. Therefore the flow developer must be
intimately aware of this implementation detail which IMHO violates the intent
of the specification.
In addition, as Guillaume stated, "Section 5.5.5.1 also gives an example of an
InOnly MEP terminated with an ERROR status"... which is clearly returned to the
consumer endpoint, otherwise there would be no value in setting the ERROR
status.
/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.
