[
https://issues.apache.org/jira/browse/CXF-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237710#comment-14237710
]
Sergey Beryozkin edited comment on CXF-4817 at 12/8/14 10:09 AM:
-----------------------------------------------------------------
Thanks for the clarification.
ContainerRequestContext has a set/get Property method, and this context is
available to the response filters so I think the data should be available - if
it does not work in your case then it is a bug - please open a JIRA issue. You
can also get HttpServletResponse passed as a context parameter to a JAX-RS
service and then to a CompletionCallback instance.
I'm still open though to the optional blocking of async context restarts
was (Author: sergey_beryozkin):
Thanks for the clarification.
ContainerRequestContext has a set/get Property method, and this context is
available to the response filters so I think the data should be available - it
it does not work in your case then it is a bug - please open a JIRA issue. You
can also get HttpServletRequest passed as a context parameter to a JAX-RS
service and then to a CompletionCallback instance.
I'm still open though to the optional blocking of async context restarts
> JAX-RS AsyncResponse implementation needs to call AsyncContext.complete after
> the request is done
> -------------------------------------------------------------------------------------------------
>
> Key: CXF-4817
> URL: https://issues.apache.org/jira/browse/CXF-4817
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Priority: Minor
> Fix For: 2.7.4, 3.0.0-milestone1
>
>
> This will help with a better recycling of threads plus will get AsyncListener
> onComplete and onError callbacks called - for the registered completion
> callbacks be notified
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
