After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

Hi all, after upgrading to Wicket 7.6.0 [1], this code [2] is causing the following error in the logs: 10:02:16.300 ERROR org.apache.wicket.protocol.ws.javax.WicketEndpoint - An error occurred in web socket connection with id : 0 java.io.IOException: Broken pipe at

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

Hi, Have you updated Tomcat version too? I don't see any reason why changes in Wicket Native WebSocket could lead to this. In the same time there were many improvements in Tomcat WebSocket code, and this might led to a regression. Martin Grigorov Wicket Training and Consulting

Re: [ANNOUNCE] CVE-2016-6793 Apache Wicket deserialization vulnerability

The site has been updated to use 1.5.17. Thanks for letting us know! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Tue, Jan 3, 2017 at 10:24 PM, durairaj t wrote: > Thank you! > > On Tue, Jan 3, 2017 at 4:11 PM, Tobias Soloschenko < >

Question/Suggestion about updating a component in aw existing page (Wicket 6.x)

Hello dear readers I am working on a web application that is very very AJAX-oriented. In other words any "displayed" page gets updated many times as a consequence of events such as (html) blur, mouse click. By updating I mean One or more fields become visible or invisible One or more fields become

Re: Question/Suggestion about updating a component in aw existing page (Wicket 6.x)

Hello dear writer :-) On Wed, Jan 4, 2017 at 2:14 PM, christophe wrote: > Hello dear readers > I am working on a web application that is very very AJAX-oriented. In other > words any "displayed" page gets updated many times as a consequence of > events such as

Re: Question/Suggestion about updating a component in aw existing page (Wicket 6.x)

Hi Christophe! Regarding (1): it sounds like you are not using models properly; Models are what makes a component “dynamic” - they pull data from a source (which could be a static string). Can you show us some code? Regarding (2): Can you show us the exceptions you get? In any case you should

Re: Question/Suggestion about updating a component in aw existing page (Wicket 6.x)

Hello Sebastian Thanks for your confirmation (it must be “manual”).. So I was not doing the wrong thing. I will “extend” the components to issue to do both updates “automatically”. As to the getSession().. It is misleading as it refers to an “application session” It does not have anything

Re: Question/Suggestion about updating a component in aw existing page (Wicket 6.x)

Hi! Yes, wicket does not automatically add changed components to the ajax response. That would be a lot of magic, which does not fit with the way the rest of the framework works (for as far as I know). I quite like how it currently works, as it’s very clear what happens. Looking at your code, I

Re: Question/Suggestion about updating a component in aw existing page (Wicket 6.x)

Hello Sebastian That was a fast feedback!! I am impressed!!! For 2) I would have to go and modify the code to get you the exact error. What I was trying to point out was simply that if Ido not BOTH replace or update the component (its state, its content) AND add to to The AjaxRequestTarget (

Re: Question/Suggestion about updating a component in aw existing page (Wicket 6.x)

Small correction: getRequest().find(AjaxRequestTarget.class) should be getRequestCycle().find(AjaxRequestTarget.class) Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 4, 2017 at 3:26 PM, Bas Gooren wrote: > Hi! > > Yes, wicket does not

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

On 04/01/2017 10:29, Francesco Chicchiriccò wrote: On 04/01/2017 10:14, Martin Grigorov wrote: Hi, Have you updated Tomcat version too? I don't see any reason why changes in Wicket Native WebSocket could lead to this. In the same time there were many improvements in Tomcat WebSocket code,

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

Hi, My question was: have you updated Tomcat lately? Maybe you have upgraded from older and working version to latest/broken one. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 4, 2017 at 10:29 AM, Francesco Chicchiriccò wrote:

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

On 04/01/2017 10:14, Martin Grigorov wrote: Hi, Have you updated Tomcat version too? I don't see any reason why changes in Wicket Native WebSocket could lead to this. In the same time there were many improvements in Tomcat WebSocket code, and this might led to a regression. Hi, this happens

Re: After upgrade to Wicket 7.6.0, WebSocket logs Broken pipe

On 04/01/2017 10:41, Martin Grigorov wrote: Hi, My question was: have you updated Tomcat lately? Maybe you have upgraded from older and working version to latest/broken one. Ah, I understand: you might be right, then. It seems that the features connected to web sockets are working fine

Re: [ANNOUNCE] WicketStuff 6.26.0 is released

Hi Martin, I've just merged the huge PR for "WICKET-6287 Switch from json.org to open-json". I've relized that this might be a problem for WicketStuff 8.0.0-M3 if you use the current master branch against Wicket 8.0.0-M3. Sorry for the inconvenience :-(. Andrea On 04/01/2017 20:42, Martin

[ANNOUNCE] WicketStuff 6.26.0 is released

Hi, WicketStuff core 6.26.0 based on Apache Wicket 6.26.0 is released and available at Maven Central. Konstantinos Karavitis (2): [portlets] Merge pull request #562 from kkaravitis/wicket-6.x [portlets] Update pom.xml Martin Tzvetanov Grigorov (2): Build against Wicket

[ANNOUNCE] WicketStuff 7.6.0 Released

WicketStuff core 7.6.0 based on Apache Wicket 7.6.0 is released and available at Maven Central. The changelog since 7.5.0 is: Martin Tzvetanov Grigorov (14): [gmap3] Fix the name of an author Build against Wicket 7.6.0-SNAPSHOT [clipboard.js] Initial commit of integration with

Re: [ANNOUNCE] WicketStuff 6.26.0 is released

Hi Andrea, Does this affect 6.26.0 anyhow ? Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jan 4, 2017 at 9:47 PM, Andrea Del Bene wrote: > Hi Martin, > > I've just merged the huge PR for "WICKET-6287 Switch from json.org to >

Re: [ANNOUNCE] WicketStuff 6.26.0 is released

no no. just the incoming (l guess) 8.0.0-M3 On 4 Jan 2017 22:22, "Martin Grigorov" wrote: > Hi Andrea, > > Does this affect 6.26.0 anyhow ? > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Wed, Jan 4, 2017 at 9:47 PM, Andrea Del