[
https://issues.apache.org/activemq/browse/SM-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianfranco Boccalon reopened SM-1667:
-------------------------------------
I dont agree with the approach that you are applying to some components: in my
opinion the right behaviour should be the suggested one only in case of
Synchronous send, while in the asynchronous mode the management of the output
message (in case of in-only usage) should be decoupled from the management of
the input message.
Doing so, should allow also avoiding using some temporary stores to keep the
exchanges that are in pending states, because in asynchronous mode I think that
the concept of "pending" is not appliable.
> 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.
