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

["Martin Grigorov (JIRA)" <ji...@apache.org>]

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

Martin Grigorov updated WICKET-5152:
------------------------------------

    Attachment: WICKET-5152.patch

Attaching a patch that may be applied to 6.x.
I don't need this for production so it is OK for me to wait for Wicket 7.0 and use Servlet 3 APIs without using reflection.
                
> Improve Wicket behavior in Servlet 3 async context
> --------------------------------------------------
>
>                 Key: WICKET-5152
>                 URL: https://issues.apache.org/jira/browse/WICKET-5152
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 6.7.0
>            Reporter: Martin Grigorov
>         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