+1 for 1.5.6. Tested build and my (small) training application, so at
least all the central parts work. Our main production app isn't migrated
yet so I can't test it yet.

I agree with Dan's assessment if WICKET-4525, that doesn't seem to be a
bug.

Carl-Eric

On Mon, 30 Apr 2012 23:41:37 +0200
Sven Meier <s...@meiers.net> wrote:

> +1 for 1.5.6
> 
> Sven
> 
> On 04/30/2012 10:05 PM, Martin Grigorov 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<seb...@gmail.com>  wrote:
> >> https://issues.apache.org/jira/browse/WICKET-4525
> >>
> >> Thanks !
> >> Sebastien.
> >>
> >> On Sun, Apr 29, 2012 at 2:56 AM, Igor
> >> Vaynberg<igor.vaynb...@gmail.com>wrote:
> >>
> >>> https://issues.apache.org/jira/browse/WICKET
> >>>
> >>> -igor
> >>>
> >>> On Sat, Apr 28, 2012 at 5:08 PM, Sebastien<seb...@gmail.com>
> >>> 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.
> >
> >
> 

Reply via email to