Re: NPE in constructor of AbstractWebSocketProcessor

2017-02-01 Thread Maxim Solodovnik
If M4 can be scheduled in reasonable time-frame I would wait ... In case you can start the VOTE this week for ex. :)) You already have +1 from me :) I have tested potentual M4 using aour main application :) On Thu, Feb 2, 2017 at 2:19 PM, Martin Grigorov wrote: > The only workaround I see is to

Re: NPE in constructor of AbstractWebSocketProcessor

2017-02-01 Thread Martin Grigorov
The only workaround I see is to reset org.apache.wicket.Session#sessionInvalidated to false in overridden #invalidateNow() via reflection :-/ The related issue is WICKET-6310. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, Feb 2, 2017 at 7:58 AM, Martin Grig

Re: NPE in constructor of AbstractWebSocketProcessor

2017-02-01 Thread Martin Grigorov
On Thu, Feb 2, 2017 at 7:21 AM, Maxim Solodovnik wrote: > Hello Martin, > > This version seems to work as expected :))) > Now the question is: How can I get M4 (or M3.1) : > +1 for a new release from me! > > > On Thu, Feb 2, 2017 at 11:41 AM, Martin Grigorov > wrote: > > > Hi Maxim, > > >

Re: NPE in constructor of AbstractWebSocketProcessor

2017-02-01 Thread Maxim Solodovnik
Hello Martin, This version seems to work as expected :))) Now the question is: How can I get M4 (or M3.1) : On Thu, Feb 2, 2017 at 11:41 AM, Martin Grigorov wrote: > Hi Maxim, > > I've fixed a nasty bug related to session management few days ago. > In case you use 8.0.0-M3 I'd suggest to t

Re: NPE in constructor of AbstractWebSocketProcessor

2017-02-01 Thread Martin Grigorov
Hi Maxim, I've fixed a nasty bug related to session management few days ago. In case you use 8.0.0-M3 I'd suggest to try with 8.0.0-SNAPSHOT! On Feb 2, 2017 6:32 AM, "Maxim Solodovnik" wrote: > Hello Martin, > > I have updated our application to wicket-8 and NPE is not reproducible > anymore >

Re: NPE in constructor of AbstractWebSocketProcessor

2017-02-01 Thread Maxim Solodovnik
Hello Martin, I have updated our application to wicket-8 and NPE is not reproducible anymore Now I have even more weird situation: on every second page reload I'm not getting WebSocketBehavior::onConnect messages (Chrome error console empty) I suspect this might be caused by my code :( The logic