You may find
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0
useful.
It has an entry about this change:
https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0#MigrationtoWicket6.0-FeedbackStorageRefactoring
Unfortunately this migration guide is not ver
On Mon, Mar 27, 2017 at 5:27 PM, Martin Grigorov wrote:
> The only way I see is to
> override org.apache.wicket.Component#getFeedbackMessages() to delegate
> to org.apache.wicket.Session#getFeedbackMessages() but you will have to do
> this for each and every component ...
> Maybe it would be bette
On Mon, Mar 27, 2017 at 7:54 AM, Trejkaz wrote:
> On Mon, Mar 27, 2017 at 4:42 PM, Sebastien wrote:
> > 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.
>
> I see... so looking at the info
On Mon, Mar 27, 2017 at 4:42 PM, Sebastien wrote:
> 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.
I see... so looking at the info() method itself, on v1.5, info() goes
into the session. But in v
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" wrote:
> Hi all.
>
> Next problem in the list. :(
>
> Most of our forms finish up their work l
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
