Aki Yoshida created CAMEL-5823:
----------------------------------
Summary: 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
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
