Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Martin Grigorov
Hi, AppEngine uses Jetty and I remembered about https://issues.apache.org/jira/browse/WICKET-5390. Here the reporter explains that Jetty won't update its SessionStore if it believes the http session didn't change. Wicket stores both o.a.w.Session and all pages rendered in the last request as attri

Re: Next Wicket 7 Release?

2015-05-15 Thread Martijn Dashorst
On Thu, May 14, 2015 at 9:43 PM, Don Ferguson wrote: > Good people of Wicket land: it’s been 3 months since 7.0.0-M5 came out. Is > an M6 or a release candidate going to be coming our way any time soon? Rest assured! We are working on it. We uncovered some nastiness with stack overflow errors,

Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Christopher Merrill
You're right!!! I didn't even look at that - I only looked to see if the log messages were there. On Thu, May 14, 2015 at 5:00 PM, Martin Grigorov wrote: > The url seems to work now! > Clicking deactivate sets the property to null. > Please confirm that it works as expected. > > Martin Grigoro

Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Christopher Merrill
Wow, that makes sense - and I _think_ it explains the symptoms I've seen with other problems as well. I'll have to re-investigate those. The issue you mentioned is marked as resolved in 6.12 and the related issue (WICKET-5473) was fixed in 6.14. We are running 6.19. So I must be reading those des

Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Martin Grigorov
On Fri, May 15, 2015 at 4:16 PM, Christopher Merrill < ch...@webperformance.com> wrote: > Wow, that makes sense - and I _think_ it explains the symptoms I've seen > with other problems as well. I'll have to re-investigate those. > > The issue you mentioned is marked as resolved in 6.12 and the re

Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Christopher Merrill
Adding an IRequestCycleListener that put a new value into the session at the end of each request DOES fix the problem. As you noted, it fixed my stripped-down example. I have tested all of the symptoms I have mentioned in previous related posts and they are ALL fixed :> Overriding our session clas

Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Martin Grigorov
On Fri, May 15, 2015 at 5:15 PM, Christopher Merrill < ch...@webperformance.com> wrote: > Adding an IRequestCycleListener that put a new value into the session at > the end of each request DOES fix the problem. As you noted, it fixed my > stripped-down example. I have tested all of the symptoms I

Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Christopher Merrill
On Fri, May 15, 2015 at 10:33 AM, Martin Grigorov wrote: > I am puzzled why people use AppEngine in first place. It has so many > restrictions. It looks like a pain to me to develop for this platform. > It does have a lot of restrictions, but if you can live with / adapt to those, GAE has a lot

Re: How could refreshing a page cause future onClick() listeners to malfunction?

2015-05-15 Thread Martin Grigorov
Please create a pull request at gae-initializer project . On May 15, 2015 6:00 PM, "Christopher Merrill" wrote: > On Fri, May 15, 2015 at 10:33 AM, Martin Grigorov > wrote: > > > I am puzzled why people use AppEngine in first place. It has so many > > restrictions. It looks like a pain to me to