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 2017/09/04 19:36:00 UTC

[jira] [Assigned] (WICKET-6458) Websocket replacing a panel which uses websockets

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

Martin Grigorov reassigned WICKET-6458:
---------------------------------------

    Assignee: Martin Grigorov

> Websocket replacing a panel which uses websockets
> -------------------------------------------------
>
>                 Key: WICKET-6458
>                 URL: https://issues.apache.org/jira/browse/WICKET-6458
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 7.8.0
>         Environment: Ubuntu 16.04
> Tomcat 8.5.20
>            Reporter: Peter Henderson
>            Assignee: Martin Grigorov
>
> I've a page which initially shows a loading panel.
> This panel uses web sockets to trigger background loading when the connected message is received.
> When the background loading has completed
> (onEvent => event.getPayload => WebSocketPushPayload => ???)
> I replace the loading place holder panel with the real data panel.
> The real data panel may also want to use web sockets, and show a loading animation.
> (Turtles all the way down)
> The problem I'm seeing, is that the WebSocketBehavior::onConnected method is not being called on the replaced panel.
> A scala sample which shows this problem.
> https://github.com/bollinger/WebSocketPanelReplace



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)