Fwd: AjaxButton does not get register to the wicket events , after it rendered by ajax request

My scenario: on an ajax event I replace a webmarkupContainer with one of my components which have some wicket IBehaviorListener. The problem is that this replace happen due to Ajax request, and the behavior gets listed on don ready: Wicket.Event.add(window, domready, function(event) {

Re: Fwd: AjaxButton does not get register to the wicket events , after it rendered by ajax request

I'm assuming that, being generated in the this event registration code happens for all components that are added explicitly, but not for any components that are added dynamically by me. That assumption is wrong. Wicket will handle all event registration code automagically. Updating a parent

Best practice for separating frontend and backend logic in wicket for testing?

There are some pages in my project which needs to interact with the backend. I have to load the data I would like to display or I have to persist form data. This works as I expect it and Wicket does here a great job. But how can I test this? For example I would like to test if page

Re: 10th aniversary of wicket

I think it would be worth to send out a press release via the ASF. Am 20.01.14 11:25, schrieb Ernesto Reinaldo Barreiro: Hi, On Mon, Jan 20, 2014 at 11:12 AM, Martin Grigorov mgrigo...@apache.orgwrote: I also would like to visit Cuba! :) Me too! But Cuba it might be a limitation for

Re: Best practice for separating frontend and backend logic in wicket for testing?

Sorry for the question. I oversight the method startPage(Page page) method Am 21.01.14 13:28, schrieb Oliver B. Fischer: There are some pages in my project which needs to interact with the backend. I have to load the data I would like to display or I have to persist form data. This works

Re: 10th aniversary of wicket

+1 for Barcelona ;) Am 20.01.2014 um 11:25 schrieb Ernesto Reinaldo Barreiro reier...@gmail.com: Hi, On Mon, Jan 20, 2014 at 11:12 AM, Martin Grigorov mgrigo...@apache.orgwrote: I also would like to visit Cuba! :) Me too! But Cuba it might be a limitation for people from USA due

Best practice for separating frontend and backend logic in wicket for testing?

There are some pages in my project which needs to interact with the backend. I have to load the data I would like to display or I have to persist form data. This works as I expect it and Wicket does here a great job. But how can I test this? For example I would like to test if page

AjaxButton does not get register to the wicket events , after it rendered by ajax request

My scenario: on an ajax event I replace a webmarkupContainer with one of my components which have some wicket IBehaviorListener. The problem is that this replace happen due to Ajax request, and the behavior gets listed on don ready: Wicket.Event.add(window, domready, function(event) {

wicket event /ajax/call/complete check if ajax response is a redirect to a new page

I want to find if the ajax response is to redirect to a new page ? I use ajax buttons even for redirect to a new wicket page, In the callback function to Wicket.Event.subscribe('/ajax/call/complete' I want to find if the ajax response is to redirect to a new page ,callback function parameter

Understanding setPageExpiredErrorPage and onUnauthorizedInstantiation

I'm trying to set a custom PageExpiredErrorPage and I'm not able to do that. It appears that the framework is calling my onUnauthorizedInstantiation method in my implementation of IUnauthorizedComponentInstantiationListener instead. Here is how I am able to reproduce: 1. User logs in 2. Wait

Re: wicket event /ajax/call/complete check if ajax response is a redirect to a new page

Hi, Better use '/ajax/call/success'. There you have the 'data' parameter or even jqXHR.responseText. You can check for redirect element and extract its content with regex. Yet another way is to use the response header: jqXHR.getResponseHeader('Ajax-Location'); Martin Grigorov Wicket Training and

Re: Understanding setPageExpiredErrorPage and onUnauthorizedInstantiation

Hi, Check your impl of org.apache.wicket.authorization.IAuthorizationStrategy Somewhere in YourApp#init you must have getSecuritySettings().setAuthorizationStrategy(...) Martin Grigorov Wicket Training and Consulting On Wed, Jan 22, 2014 at 7:31 AM, jchappelle jchappe...@4redi.com wrote: I'm