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

Posted to commits@wicket.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/03/23 16:10:43 UTC

[jira] [Commented] (WICKET-6345) Check for non-null PushBuilder before trying to use it

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

ASF subversion and git services commented on WICKET-6345:
---------------------------------------------------------

Commit 49232763b2d5727d5b08850afe25d5040773b8d2 in wicket's branch refs/heads/master from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=4923276 ]

WICKET-6345 Check for non-null PushBuilder before trying to use it


> Check for non-null PushBuilder before trying to use it
> ------------------------------------------------------
>
>                 Key: WICKET-6345
>                 URL: https://issues.apache.org/jira/browse/WICKET-6345
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-http2
>    Affects Versions: 8.0.0-M4
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>            Priority: Minor
>             Fix For: 8.0.0-M5
>
>
> According to the latest Servlet 4 development the Web container should return null when HTTP2 Push is not supported for the current request.
> Wicket PushBuilder abstractions should take this into account to avoid failing with NullPointerException.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)