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 2016/12/20 08:45:58 UTC

[jira] [Reopened] (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 ]

Martin Grigorov reopened WICKET-6296:
-------------------------------------

Reopening this ticket because I think I remember the use case in WICKET-6152. I'll have to retest!

> 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
>             Fix For: 6.26, 7.6.0, 8.0.0-M3
>
>
> 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)