[
https://issues.apache.org/jira/browse/WICKET-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152913#comment-16152913
]
Martin Grigorov edited comment on WICKET-6458 at 9/4/17 8:10 PM:
-----------------------------------------------------------------
I had the desire to work on this but I have no time to fight with custom builds.
I understand that SBT is better for you but it slows me down. I've spend half
an hour trying to find how to start your demo app in debug mode in my IDE and
teach it to use Wicket -SNAPSHOT from my local ~/.m2.
Normal Wicket quickstart (http://wicket.apache.org/start/quickstart.html) would
make me try again.
was (Author: mgrigorov):
I had the desire to work on this but I have no time to fight with custom builds.
I understand that SBT is better for you but it slows me down. I've spend half
an hour trying to find how to start your demo app and teach it to use Wicket
-SNAPSHOT from my local ~/.m2.
> 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-native-websocket
> Affects Versions: 7.8.0
> Environment: Ubuntu 16.04
> Tomcat 8.5.20
> Reporter: Peter Henderson
> Assignee: Martin Grigorov
> Priority: Minor
>
> 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)
