Hi,
I have 2 pages, each with a feedback panel. Page2 does the following:
setACookie();
Session.get().info("blah");
setResponsePage(Page1.class);
The problem I have is that "blah" is never displayed in the feedback
panel of Page1. I stepped in the request processing code and found that
setResp
--
> To unsubscribe, e-mail: users-unsubscribe@.apache
> For additional commands, e-mail: users-help@.apache
>
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePage-swallows-my-session-feedba
-
To unsubscribe, e-mail: users-unsubscribe@.apache
For additional commands, e-mail: users-help@.apache
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePage-swallows-my-session-feedback-messages-tp4650274p4650278.ht
to the page. Otherwise Wicket will throw a missing component
>>> exception in dev mode.
>>>
>>> 3-My use case; feedback messages registered in the session can be
>>> swallowed by a feedback pan
itutes must be
>>> added to the page. Otherwise Wicket will throw a missing component
>>> exception in dev mode.
>>>
>>> 3-My use case; feedback messages registered in the session can be
>>> swallowed by a feedback panel in the throw
ional commands, e-mail: users-help@.apache
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePage-swallows-my-session-feedback-messages-tp4650274p4650278.html
Sent from the Users forum mailing list archive at Nabble.com.
plete picture and am just now
making some sense of how Wicket handles redirects and responses.
Regards,
Bertrand
-
To unsubscribe, e-mail: users-unsubscribe@.apache
For additional commands, e-mail: users-help@.apache
--
View this message in context:
http://apache-wicket
gt;>>> I'm also wondering why, when setResponsePage() is used, the current
>>>>> page
>>>>> is still rendered. I can think of 3 reasons why this should be
>>>>> avoided:
>>>>> 1-Performance; it's wasteful to render compon
To unsubscribe, e-mail: users-unsubscribe@.apache
For additional commands, e-mail: users-help@.apache
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/setResponsePage-swallows-my-session-feedback-messages-tp4650274p4650278.ht
es all the session
>>>>>>> messages. After the client follows the 302 and requests Page1, there
>>>>>>> are
>>>>>>> no more session messages to display.
>>>>>>>
>>>>>
Hi,
Here is my later response.
I see two ways to solve this:
1) Use setResponsePage(pageInstance) as I described in my previous response:
setMyCookie();
PageB pageB = new PageB();
pageB.info("some text");
setResponsePage(pageB);
This way the feedback is associated with a component (pageB) and
Hi Martin,
Thanks for your answer and code. Indeed, in my case, option 2 is most
desirable because the session message is set in a completely different
place than where the redirect is done.
NonResettingRestartException works great when thrown from a page
constructor. However, when thrown fr
Hi Bertrand,
On Mon, Jul 2, 2012 at 11:21 PM, Bertrand Guay-Paquet
wrote:
> Hi Martin,
>
> Thanks for your answer and code. Indeed, in my case, option 2 is most
> desirable because the session message is set in a completely different place
> than where the redirect is done.
>
> NonResettingRestar
Hi,
Issues WICKET-4636 and WICKET-4637 were created.
Bertrand
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Hi Martin,
Following Andrea's comments from issue Wicket-4637, I modified the
NonResettingRestartException to fix the error I reported.
Here's the modified version:
public class NonResettingRestartException extends ReplaceHandlerException {
public NonResettingRestartException(final Class
15 matches
Mail list logo
