camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5823) CxfConsumer should not populate the cxf response with the original input message if the cxfExchange is oneway
Date Tue, 27 Nov 2012 08:43:58 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504458#comment-13504458
] 

Willem Jiang commented on CAMEL-5823:
-------------------------------------

This issue is introduced by the fix of CAMEL-5810. Thanks for the Aki quick patch.

For the exception handling on the CxfConsumer side, we don't intend to let CxfConsumer to
do further work.
As the exception is came from camel processor chain which should be handled by the camel error
handler.
In this Cxf Consumer just need to marshal the exception to the client side.
                
> CxfConsumer should not populate the cxf response with the original input message if the
cxfExchange is oneway
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5823
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5823
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>    Affects Versions: 2.10.2
>            Reporter: Aki Yoshida
>            Assignee: Willem Jiang
>         Attachments: camel-cxf-oneway-route-20121126.patch
>
>
> When you have a camel route from a CXF oneway endpoint to some endpoint, cxfConsumer
currently uses the input message to fill the cxf's response message at the cxf endpoint. This
can lead to a problem in CXF as there can be an exception raised during this step.
> To avoid this issue, I think we should not fill the cxf response if the cxf's exchange
is set to oneway.
> I have attached a test case and a possible fix for this issue.
> There is also one question regarding this part of the processing in CxfConsumer. I noticed
that there are no exception handling in that part in camel and therefore the exception is
not visible in camel. I was not sure if this was intentional or if we should be setting the
exception to camel's exchange in that case so that this exception is also picked up by camel.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message