Hi Willem, I updated the patch for CXF-3788 to avoid the problem you discovered for the original patch. I have tested the updated patch against a jaxw disptach test case in CXF. I would like to verify that this correction works for the test case you had without using this request property setting. Is your test case in the camel-cxf test folder? If not, could you tell me which one?
Thanks. regards, aki 2011/9/9 Willem Jiang (JIRA) <j...@apache.org>: > > [ > https://issues.apache.org/jira/browse/CAMEL-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Willem Jiang resolved CAMEL-4429. > --------------------------------- > > Resolution: Fixed > Fix Version/s: 2.8.2 > > Applied patch into trunk and Camel 2.8.x branch. > >> CXFProducer should tell CXF to ignore the part response handling when it >> uses MESSSAGE dataformat >> -------------------------------------------------------------------------------------------------- >> >> Key: CAMEL-4429 >> URL: https://issues.apache.org/jira/browse/CAMEL-4429 >> Project: Camel >> Issue Type: Improvement >> Components: camel-cxf >> Reporter: Willem Jiang >> Assignee: Willem Jiang >> Fix For: 2.8.2, 2.9.0 >> >> >> IN CXF-3788, CXF HTTPConduit will handle the partial response when the HTTP >> response code is 202 nor matter the operation is oneway or not. It will >> cause the camel-cxf producer wait for the response for server for ever. >> CXF-3796 introduces a new message header to help us to workaround this >> issue, we need to set this header in CxfProducer when the data format is >> MESSAGE. >> > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
