[
https://issues.apache.org/jira/browse/CXF-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101546#comment-13101546
]
Daniel Kulp commented on CXF-3796:
----------------------------------
Aki,
I just added an @Ignored test to DispatchClientServerTest in systests/jaxws
that you could look at to see the reason this is needed. Basically, if using
a Dispatch client in Message mode (likely PAYLOAD mode as well), and you just
have a raw XML message but no WSDL to associate it with, there isn't a way to
really determine if the method you are about to invoke with it is a one-way or
a two way. Thus, Camel just calls the equivalent of "invoke". With the new
behavior, this causes the client to hang. The property Willem introduced
allows Camel to set it to kind of retain the old behavior. That said, I don't
agree with that approach, but I need to think about it a bit. Suggestions
welcome. :-)
> 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
