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

I'm seeing problems throughout our app where refreshing the page causes other event listeners to then malfunction. These are trivially simple listeners, like: Link customer_link = new Link(org_link) { @Override public void onClick() { setResponsePage(new

wicket 6.19, url encryption, session invalidate , redirect to wicket page

wicket 6.19 url encryption, after user logout, redirect to new WicketPage() is failing with http 404 error (page not found) as session is destroyed and key for encryption was in session which is no more available. as per documentation (KeyInSessionSunJceCryptFactory)

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

I added that line, along with Debug.log.out(the test attribute is: + getSession().getAttribute(test)); in the onSubmit() method of the AjaxButton. If I DO NOT refresh the page before pressing the button, then it prints the message with the date in the logs. If I do refresh the page,

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

Hi, My guess is that there is some problem with the saving of the page in the backing stores. Try by disabling page recreation for expired pages, see IPageSettings, If I'm right then you should start seeing PageExpiredPage after clicking the link. The next step is will be to find why the pages

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

Can you try something else: in onClick() add code like: getSession.setAttribute(test, new Date()) Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, May 14, 2015 at 11:18 PM, Christopher Merrill ch...@webperformance.com wrote: Thanks for your help, Martin!

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

I'll do that. It'll take a few minutes to deploy that back up to AppEngine. But I don't think that code will be executed - I feel pretty confident that the event listeners are not being invoked. At least, my debug statements in the event listener do not get into the AppEngine logs. Chris On

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

Thanks for your help, Martin! I turned off page recreation by adding: getPageSettings().setRecreateMountedPagesAfterExpiry(false); to my Application.init() method. There is no change in the behavior, either locally or in AppEngine -- i.e. no page expired errors. You can observe the behavior

Re: wicket 6.19, url encryption, session invalidate , redirect to wicket page

Hi, Consult with CryptoMapper's javadoc to see how to mount a page that will not be managed by CryptoMapper. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, May 14, 2015 at 11:20 PM, fachhoch fachh...@gmail.com wrote: wicket 6.19 url encryption, after

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

I added the getSession().setAttribute() into the page constructor. When I hit the page, I see two lines in the AppEngine logs. The first is for the URL I put in the browser (/portal/pages/Test), which indicates a 302 response to the browser and the log entry also contains the debug message that I

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

OK, then also put the same line in some constructor that is invoked. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, May 14, 2015 at 11:32 PM, Christopher Merrill ch...@webperformance.com wrote: I'll do that. It'll take a few minutes to deploy that back

Next Wicket 7 Release?

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? -Don - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For

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

Oh, and what you probably also wanted to know: When I press refresh on the page, the message from the constructor does not appear in the logs again. Also nothing after pressing the button (which does nothing). On Thu, May 14, 2015 at 4:50 PM, Christopher Merrill ch...@webperformance.com wrote:

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

The url seems to work now! Clicking deactivate sets the property to null. Please confirm that it works as expected. Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Thu, May 14, 2015 at 11:50 PM, Christopher Merrill ch...@webperformance.com wrote: I added the

Re: Setting a button press on hitting the enter key from the keyboard

Hello Vishy, Iam facing the same problem which you were facing. The link which you posted is not available. Can you please share the solution with me. Thanks, Akshay. -- View this message in context: