[
https://issues.apache.org/jira/browse/CXF-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101228#comment-13101228
]
Aki Yoshida commented on CXF-3796:
----------------------------------
Hi Willem,
I am not sure whether this change works for cxf trunk. We needed to comply with
the basic profile to return an HTTP response with no soap content for oneway
calls in cxf trunk (for CXF-3768, CXF-366, and CXF-981).
Basically, the server endpoint will return an HTTP 202 with no content for
oneway calls or those with the decoupled ws-a replyTo channel.
And when the response has no content and this handlingPartialResponse property
is set to false, I think you will be getting some exception when you try to
read the content later.
I am wondering if my assumption is right and if so, if there is another way of
resolving this issue.
regards, aki
> Introduce an header to disable the handling the PartialResponse when the
> response code is 202
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-3796
> URL: https://issues.apache.org/jira/browse/CXF-3796
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.3.7, 2.4.3
>
>
> The change of CXF-3788 breaks a test of camel-cxf which is using the MESSAGE
> data format to route the oneway request.
> When the camel-cxf endpoint working in the MESSAGE data formate, it know
> nothing about the binding operation of the request and response, so it just
> treat it as two way request. The change of CXF-3788 just eat up the response,
> and camel route will wait for the response forever.
> I'd like to introduce a message header to disable the handling the
> PartialResponse message in the HTTPConduit to fix the test failed of
> camel-cxf.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
