You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Vit Springl (JIRA)" <ji...@apache.org> on 2016/12/08 16:35:58 UTC
[jira] [Updated] (WICKET-6296) Not possible to add
WebSocketBehavior in ajax request
[ https://issues.apache.org/jira/browse/WICKET-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vit Springl updated WICKET-6296:
--------------------------------
Description: Due to a change in WICKET-6152 the renderHead method in BaseWebSocketBehavior is never called if the WebSocketBehavior is added in an Ajax request. This makes using web sockets more complicated in a single ajax page scenario. -(Wouldn't it be possible to use page metadata instead of requestcycle metadata, for instance?)- (was: Due to a change in WICKET-6152 the renderHead method in BaseWebSocketBehavior is never called if the WebSocketBehavior is added in an Ajax request. This makes using web sockets more complicated in a single ajax page scenario. (Wouldn't it be possible to use page metadata instead of requestcycle metadata, for instance?))
> Not possible to add WebSocketBehavior in ajax request
> -----------------------------------------------------
>
> Key: WICKET-6296
> URL: https://issues.apache.org/jira/browse/WICKET-6296
> Project: Wicket
> Issue Type: Bug
> Components: wicket-native-websocket
> Affects Versions: 7.3.0, 8.0.0-M1, 6.23.0
> Reporter: Vit Springl
> Assignee: Martin Grigorov
>
> Due to a change in WICKET-6152 the renderHead method in BaseWebSocketBehavior is never called if the WebSocketBehavior is added in an Ajax request. This makes using web sockets more complicated in a single ajax page scenario. -(Wouldn't it be possible to use page metadata instead of requestcycle metadata, for instance?)-
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)