Hi,
Wicket uses temporary Sessions for stateless application.
Adding a feedback message to such session will live till the end of the
current request. Since the response page is rendered in the same
request/response cycle the feedback messages should be still reachable.
On Mon, Apr 29, 2013 at
Hi,
This is not the behavior I'm getting. I created a stateless page with this:
add(new FencedFeedbackPanel(feedback));
add(new StatelessLinkVoid(success) {
@Override
public void onClick() {
getSession().info(Success message (without
On Tue, Apr 30, 2013 at 5:44 PM, Bertrand Guay-Paquet
ber...@step.polymtl.ca wrote:
Hi,
This is not the behavior I'm getting. I created a stateless page with this:
add(new FencedFeedbackPanel(feedback**));
add(new StatelessLinkVoid(success) {
@Override
Hi,
Since you are redirecting to another stateless page
(setResponsePage(Class)), the browser is redirected to the new url which
creates a new, temporary session for the second request.
If you don't link to another page (so no setResponsePage call), it will
work, since the response is
On Tue, Apr 30, 2013 at 5:58 PM, Bas Gooren b...@iswd.nl wrote:
Hi,
Since you are redirecting to another stateless page
(setResponsePage(Class)), the browser is redirected to the new url which
creates a new, temporary session for the second request.
If you don't link to another page (so no
Thanks for your replies. I can confirm the described behavior without
setResponsePage().
I created issue WICKET-5165 for this.
On 30/04/2013 12:05 PM, Martin Grigorov wrote:
On Tue, Apr 30, 2013 at 5:58 PM, Bas Gooren b...@iswd.nl wrote:
Hi,
Since you are redirecting to another stateless
Hello,
When using the Sessions info(), error() and success() methods, and the
session is not bound, the messages are lost. This can happen easily when
on stateless pages. The fix for this is easy: I need to make sure the
session is bound and call Session.bind().
However, I think it would be
