[
https://issues.apache.org/jira/browse/CXF-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CXF-2982.
-------------------------------
Resolution: Fixed
Applied patch with suggestion of DanKulp
Here is the mail thread[1] about it.
[1]http://cxf.547215.n5.nabble.com/CXF-continuation-enhancement-td2800561.html#a2800561
> Don't throw the SuspendedInvocationException when call the suspend() method
> of CXF continuation
> -----------------------------------------------------------------------------------------------
>
> Key: CXF-2982
> URL: https://issues.apache.org/jira/browse/CXF-2982
> Project: CXF
> Issue Type: Improvement
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.3
>
> Attachments: cxf-2982.patch
>
>
> Current CXF Continuation suspend implementation is based on throw
> SuspendedInvocationException, This implementation has a shortcoming which
> cannot call the other framework's async API after continuation suspend is
> called as Jetty7 does.
> So I introduce a flag of Message.CONTINUATION_SUSPENDED to break out current
> interceptor chain as the SuspendedInvocation does, but It will make CXF
> continuation API more easy to use and it supports the Jetty7 continuation or
> Servlet3 suspend resume semantics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
