Hi,
Yes, the message is lost. For such a use case, you have to use
Session.get().info(), so your message remains available after the redirect.
Best regards,
Sebastien
On Mar 27, 2017 03:19, "Trejkaz" <trej...@trypticon.org> wrote:
> Hi all.
>
> Next problem in the list. :(
>
> Most of our forms finish up their work like this:
>
> info("Successfully did something")
> setResponsePage(SomePage.class);
>
> And in the tests we check it like this:
>
> tester.assertRenderedPage(SomePage.class);
> tester.assertInfoMessages("Successfully did something");
>
> After updating to Wicket 6.26.0, this test now fails because there are
> supposedly no info messages.
> I tried 6.13.0 and got the same result there.
>
> Investigation:
> * This time the real application does exhibit the issue.
> * A breakpoint in the IFeedbackMessageFilter verifies that it does get
> called and that every single call returns false.
>
> At this point I can't figure out why the messages are being deleted so
> again, asking here whether we're doing something wrong, or whether
> this is a bug.
>
> Demo code here: https://github.com/trejkaz/wicket-feedback-problems
>
> TX
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
