[jira] [Commented] (WICKET-6296) Not possible to add WebSocketBehavior in ajax request

["Martin Grigorov (JIRA)" <ji...@apache.org>]

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

Martin Grigorov commented on WICKET-6296:
-----------------------------------------

A (stateful) page could be rendered many times. In this case the header contributions should be done for each of them.

Another solution would be to remove the check for "isAjax" and contribute a JS HeaderItem with id. This way Wicket will not insert it twice in the page's DOM.
Do you want to give this a try and send us a Pull Request / attach a patch ?

> 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)