cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-7140) Multiple calls to AsyncResponse.cancel() returns different values
Date Wed, 16 Nov 2016 22:59:58 GMT

     [ https://issues.apache.org/jira/browse/CXF-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Beryozkin resolved CXF-7140.
-----------------------------------
       Resolution: Fixed
         Assignee: Sergey Beryozkin
    Fix Version/s: 3.0.12
                   3.1.9
                   3.2.0

Thanks for the patch, unfortunately, before your patch has been applied, only a (system) test
testing a single cancel was available.  

> Multiple calls to AsyncResponse.cancel() returns different values
> -----------------------------------------------------------------
>
>                 Key: CXF-7140
>                 URL: https://issues.apache.org/jira/browse/CXF-7140
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.1.8
>            Reporter: Andy McCright
>            Assignee: Sergey Beryozkin
>             Fix For: 3.2.0, 3.1.9, 3.0.12
>
>
> 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().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message