A well-deserved vacation! I debugged the quickstart, and the issue is caused by the WICKET-4286 fix and the way re-rendered behaviors' requests now target a renderCount less than that of the page.
(non-binding) -1 On Mon, Apr 30, 2012 at 1:05 PM, Martin Grigorov <[email protected]>wrote: > Can someone of the Wicket devs verify the problem and cancel the release? > Or +1 it otherwise ... > > P.S. I'm on vacation without IDEs around :-) > > On Sun, Apr 29, 2012 at 1:34 PM, Sebastien <[email protected]> wrote: > > https://issues.apache.org/jira/browse/WICKET-4525 > > > > Thanks ! > > Sebastien. > > > > On Sun, Apr 29, 2012 at 2:56 AM, Igor Vaynberg <[email protected] > >wrote: > > > >> https://issues.apache.org/jira/browse/WICKET > >> > >> -igor > >> > >> On Sat, Apr 28, 2012 at 5:08 PM, Sebastien <[email protected]> wrote: > >> > Hi again... (and sorry again) > >> > > >> > This time it is a real issue I am facing with the 1.5.6 build 2 > (whereas > >> it > >> > was working using 1.5.5). > >> > > >> > To sum up, the issue is related to an http-post, where a required text > >> > field is sent through a form by a javascript 'submit' command, which > >> > command has been transmitted to the client side via an ajax-behavior, > and > >> > iif the validation has failed at the very first try. In that case, the > >> > behavior's script transmitted to the client seems to not be executed > (the > >> > page is immediately re-rendered after the "Invoking pre-call > >> handler(s)..." > >> > step). Despite the research I made on revolved issues for 1.5.6, I did > >> not > >> > find any related issue that may cause this one. > >> > > >> > I have prepared a quickstart (and more infos about the use case) in > case > >> > you want to look at this... > >> > Just tell me where I have to send/post it. > >> > > >> > Thanks and best regards, > >> > Sebastien. > >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com >
