[
https://issues.apache.org/jira/browse/CXF-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-5417:
------------------------------
Attachment: patch-connection-callback.txt
Hi Sergey,
I have checked Servlet3Continuation.onError(AsyncEvent event): it's not being
called in case of disconnect / abort. Following your comments (thanks a lot as
always) I was able to figure out the way to pass this kind of exceptions from
AbstractHTTPDestination up to AsyncResponseImpl, please review my patch
(patch-connection-callback.txt) when you have time. I am still working on JUnit
test cases, it turns out to be a bit tricky though but I should come up with
ones soon :) Anyway, I eager to hear your feedback, I have tested the
implementation on Jetty and Tomcat and it works fine.
Thanks.
Andriy
> Support optional JAX-RS 2.0 ConnectionCallback
> ----------------------------------------------
>
> Key: CXF-5417
> URL: https://issues.apache.org/jira/browse/CXF-5417
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS, Transports
> Reporter: Sergey Beryozkin
> Priority: Minor
> Attachments: patch-connection-callback.txt
>
>
> https://jax-rs-spec.java.net/nonav/2.0/apidocs/javax/ws/rs/container/ConnectionCallback.html
> lets JAX-RS 2.0 applications receive the notifications when a given client
> has disconnected.
> We can probably build something on top of the Jetty-specific connector and
> also enhance CXF Continuation API.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
