Thanks for looking Martin
On 3 November 2016 at 09:07, Martin Grigorov wrote:
> Hi,
>
> It is a bug in Wicket Native WebSocket.
> https://github.com/apache/wicket/blob/d9d142b0738e289e639165523c4190
> 727e281519/wicket-native-websocket/wicket-native-
> websocket-core/src/main/java/org/apache/w
Hi,
It is a bug in Wicket Native WebSocket.
https://github.com/apache/wicket/blob/d9d142b0738e289e639165523c4190727e281519/wicket-native-websocket/wicket-native-websocket-core/src/main/java/org/apache/wicket/protocol/ws/api/AbstractWebSocketProcessor.java#L310
returns a null and still we try to pu
Hi all.
wicket 7.3
tomcat 8.5.5
I'm starting to see many more exceptions in relation to web sockets.
[1]
I have a HttpSessionListener, which sends a message to an actor when a
session is destroyed (aka user logout). The actor eventually broadcasts a
web socket message.
Am I doing something
