Re: Joda-time dependency

Hi Maxim, wicket-jquery-ui do not relied on wicket-datetime. On wicket-jquery-ui < 8.x, java datetime are handled by org.threeten api (which is ISO to java8 datetime) Best regards, Sebastien On Sat, Sep 16, 2017 at 2:26 PM, Maxim Solodovnik wrote: > I'm using kendo

Re: WebSocket and timeout

Hi, On Sat, Sep 16, 2017 at 1:32 PM, Manfred Bergmann mb@ wrote: > Found a different solution. > > Followed the advice here: > https://issues.apache.org/jira/browse/WICKET-5453 > > Where you can set the default idle timeout on the > WebSocketServerContainerInitializer. > This is a good start!

Re: Joda-time dependency

I'm using kendo date-time picker from wicket-jquery-ui And I believe it depends on wicket-datetime Will try to do my best on migration then you will review :) On Sat, Sep 16, 2017 at 7:13 PM, Martin Grigorov wrote: > Hi Maxim, > > Since I do not use wicket-datetime in my

Re: Joda-time dependency

Hi Maxim, Since I do not use wicket-datetime in my apps I also wanted to break it hard by replacing Joda-Time with Java 8 classes. But people who use it expressed concerns that it will be hard to migrate this way. Everyone will have to do the same for his/her application. I remember Igor even

Re: WebSocket and timeout

Hi, On Sat, Sep 16, 2017 at 1:32 PM, Manfred Bergmann wrote: > Found a different solution. > > Followed the advice here: > https://issues.apache.org/jira/browse/WICKET-5453 > > Where you can set the default idle timeout on the > WebSocketServerContainerInitializer. >

Re: WebSocket and timeout

Found a different solution. Followed the advice here: https://issues.apache.org/jira/browse/WICKET-5453 Where you can set the default idle timeout on the WebSocketServerContainerInitializer. Manfred -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html