Hi Andrei, This case (i.e., a oneway call needs to process a non empty http 200 response) occurs in one specific configuration options in WS-RM.
WS-RM supports several options for embedding (or exchanging) the acknowledgement messages that are sent from the message receiver back to the message sender. For oneway application services, you can configure these acknowledgement messages to be either sent back directly in the http response or sent back using a separate http request. In the former case, the response, if it is there, needs to be processed as it may contain the SOAP message with the WS-RM acknowledgement header. How does the NPE case you are analyzing look like? regards, aki 2012/4/12 Andrei Shakirin <[email protected]>: > Hi, > > I am analysing NPE for case of non-empty oneWay operation response. > > Digging into HTTPConduit code I found two situations where non-empty oneWay > response is interpreted as valid in- message and processed: > > 1. oneWay chunked partial response > > 2. twoWay decoupled partial response > > Criteria to process this responses even if exchange is onWay are: > HttpHeaderHelper.TRANSFER_ENCODING = HttpHeaderHelper.CHUNKED or > HttpHeaderHelper.CONNECTION = HttpHeaderHelper.CLOSE > > Just curious what is the real use case for client to process oneWay > responses? Is it standard or CXF extensions? > > Regards, > Andrei.
