When we incorporated CXF 3.1.8 into our builds, our CTS testing team found some failures related to the AsyncResponse.cancel(...) methods. According to the spec, once the AsyncResponse has been canceled, subsequent calls to cancel should return true.
It looks like one of the changes in
CXF-7037 changed the order of things in the doCancel method – and those changes result in false getting returned when calling cancel(...) a second time.
I have written some tests that demonstrate the expected CTS behavior - and they fail with the current code, but pass when reverting the order change in doCancel().