[
https://issues.apache.org/activemq/browse/SMXCOMP-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58230#action_58230
]
Pavel Drasil edited comment on SMXCOMP-719 at 3/14/10 11:00 AM:
----------------------------------------------------------------
Considering whether an issue is or is not a release blocker is of course out of
my competencies. However, personally, I find the fact that properties of JBI
fault messages are lost during traversing the camel component a serious
problem. And what is worse, this is an undocumented change in the behavior of
the servicemix-camel component, which can break the applications built upon the
2009.01 camel component, distributed with the latest official Servicemix
releases.
was (Author: drasil):
Considering whether an issue is or is not a release blocker is of course
out of my competencies. However, personally, I find the fact that headers of
JBI fault messages are lost during traversing the camel component a serious
problem. And what is worse, this is an undocumented change in the behavior of
the servicemix-camel component, which can break the applications built upon the
2009.01 camel component, distributed with the latest official Servicemix
releases.
> CamelProviderEndpoint does not copy "out" Camel message headers to JBI
> "fault" message properties
> -------------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-719
> URL: https://issues.apache.org/activemq/browse/SMXCOMP-719
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-camel
> Affects Versions: servicemix-camel-2009.02
> Reporter: Pavel Drasil
> Assignee: Jean-Baptiste Onofré
>
> Headers of the "out" Camel message are not copied to JBI "fault" message
> properties in CamelProviderEndpoint.onFailure(). This is troublesome for
> example when servicemix-camel is used together with servicemix-http, which
> reads SOAP fault code and reason from JBI fault message properties. In
> servicemix-camel-2009.01 this worked correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
