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
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
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
Thank You very much!! :)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WicketMessage-Can-t-instantiate-page-using-constructor-public-com-mycompany-StartPage-An-exception-h-tp4677445p4677447.html
Sent from the Users forum mailing list archive at Nabble.com.
Hi,
apparently your injection isn't set up correctly, thus managerLocal is null.
Please take a look how the CDI example does it in wicket-examples, e.g.
the following is missing at least:
new CdiConfiguration().configure(this);
Have fun
Sven
On 26.03.2017 17:53, Sokab wrote:
Hi
Hi Everyone! I am new and I want to learn to Wicket. When I create new simple
project with Wicket everything is ok but when I try add EJB class to Wicket
(WebPage) always i have this same error:
"WicketMessage: Can't instantiate page using constructor 'public
com.mycompany.StartPage()'. An