You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Andrea Del Bene (JIRA)" <ji...@apache.org> on 2013/04/29 15:24:16 UTC

[jira] [Commented] (WICKET-5152) Improve Wicket behavior in Servlet 3 async context

    [ https://issues.apache.org/jira/browse/WICKET-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644476#comment-13644476 ] 

Andrea Del Bene commented on WICKET-5152:
-----------------------------------------

So it will be applied only to version 7 (without using reflection)? I don't need it too in 6.x, I'm just curios about it...
                
> Improve Wicket behavior in Servlet 3 async context
> --------------------------------------------------
>
>                 Key: WICKET-5152
>                 URL: https://issues.apache.org/jira/browse/WICKET-5152
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.7.0
>            Reporter: Martin Grigorov
>             Fix For: 7.0
>
>         Attachments: WICKET-5152.patch
>
>
> At the moment it is not possible to use javax.servlet.ServletRequest#startAsync() in Wicket resources because the http response is committed at the end of the request cycle by calling HttpServletResponse#flushBuffer().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira