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

Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/09/17 14:45:34 UTC

[jira] [Resolved] (WICKET-5701) WebSocketRequestHandler is not set as a scheduled and thus RequestCycle#find(AjaxRequestTarget.class) doesn't work

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

Martin Grigorov resolved WICKET-5701.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 7.0.0-M4
                   6.18.0

> WebSocketRequestHandler is not set as a scheduled and thus RequestCycle#find(AjaxRequestTarget.class) doesn't work 
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-5701
>                 URL: https://issues.apache.org/jira/browse/WICKET-5701
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-native-websocket
>    Affects Versions: 6.17.0
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 6.18.0, 7.0.0-M4
>
>
> As discussed at https://groups.google.com/d/topic/wicket-jquery-ui/fw6TdyO5o18/discussion AbstractWebSocketProcessor doesn't schedules the WebSocketRequestHandler in the request cycle and thus it is not reachable for user code via RequestCycle#find(Class) API.
> Additionally the configured application RequestCycle listeners are not notified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)