[
https://issues.apache.org/jira/browse/WICKET-5701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137161#comment-14137161
]
ASF subversion and git services commented on WICKET-5701:
---------------------------------------------------------
Commit 087c0a26c90f433748c3132b463a640c41cbb0f2 in wicket's branch
refs/heads/master from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=087c0a2 ]
WICKET-5701 WebSocketRequestHandler is not set as a scheduled and thus
RequestCycle#find(AjaxRequestTarget.class) doesn't work
(cherry picked from commit 482c595f5c1b2ee5032140ed0ede79d9f48af26f)
> 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)
