[
https://issues.apache.org/jira/browse/CXF-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103576#comment-13103576
]
Aki Yoshida commented on CXF-3796:
----------------------------------
Hi Dan, Willem,
I updated the original ticket CXF-3788 with the patch to detect this condition
and avoid blocking the call. Dan's new jaxws systests (version 1 and version2)
that are supposed to simulate the problem reported in this ticket are activated
and running fine. So, I think we do not need this extra parameter to configure
the behavior. This needs to be verified.
As mentioned in my last comment in CXF-3788, we should be moving one of the
constants from rt-ws-addr to api. Comments?
thanks.
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
