Hi, See https://issues.apache.org/jira/browse/WICKET-5453
Martin Grigorov Wicket Training and Consulting On Fri, May 30, 2014 at 4:18 PM, Jan Moxter <jan.mox...@innobix.com> wrote: > Hello Wickets, > > > > > I am doing some extensive testing with the native-websocket implementation > in preparation for wicket-7 conversion of my apps. The websocket part is > going to be used for an internal messaging system which sends/broadcasts > system notifications to the logedin users. This all works thanks to the > magic of wicket really well implementing the WebSocketBehavior, but.... > > > Ok the problem I got is how to change the maxIdleTime for an > implementation with Jetty-9.1 due to timout problesm. Normally you have an > InitParameter in the web.xml, but the WebSocketUpgradeFilter is actually > not initialized by reading the web.xml but by the > WicketServerApplicationConfig d uring class reading as specified in the > javax.websocket.api. > So there are actually no initparameters passed to the filter! The only way > I figured out how to set the maxIdleTime would be in the jetty general > configuration for all applications, but i really would like to be able to > set it just for one application only. > > > Any idea how to set these parameter? > > > By the way this also applies to the other parameters like > MaxBinaryMessageBufferSize, setMaxTextMessageBufferSize etc. which are part > of the javax.websocket.Session API. > > > > > Thanks a lot for the help > > > > Jan Moxter > >
