You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2010/11/22 18:36:14 UTC

[jira] Resolved: (CXF-3133) Refactoring JAXRSInvoker to support CXF continuation better

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

Sergey Beryozkin resolved CXF-3133.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4
         Assignee: Sergey Beryozkin  (was: Willem Jiang)

> Refactoring JAXRSInvoker to support CXF continuation better 
> ------------------------------------------------------------
>
>                 Key: CXF-3133
>                 URL: https://issues.apache.org/jira/browse/CXF-3133
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Willem Jiang
>            Assignee: Sergey Beryozkin
>             Fix For: 2.3.1, 2.4
>
>         Attachments: jaxrs.patch
>
>
> I did some clean up work[1] on the CxfRsInvoker in Camel to let it work better with CXF 2.3.0 continuation API.
> Current JAXRSInvoker is not friendly to CXF continuation API, and the method
> {code}
> public Object invoke(Exchange exchange, Object request)
> {code}
> is stateful and can't be called by the continuation resume process.
> [1]http://svn.apache.org/viewvc?rev=1036343&view=rev

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.