Please provide a small quickstart showcasing the problem to get more help
because based on these information it should work.
Attila
2011/10/15 Mathias Nilsson wicket.program...@gmail.com
Oh, And I've also tried putting
org.springframework.web.filter.CharacterEncodingFilter as the first filter
Hi,
In 1.5, the request cycle (indirectly) contains a stack of request handlers.
According to the Java docs, it seems the purpose is to allow a request
handler to execute another request handler in its respond() method by
calling the execute() method in the request cycle. However:
a) There seems
I'll try to get some time to build a test to get some timings.
-Original Message-
From: Jeremy Thomerson [mailto:jer...@wickettraining.com]
Sent: Sunday, 16 October 2011 11:55 AM
To: users@wicket.apache.org
Subject: Re: Efficiency of 1.5 MountMapper weighted/matching algorithm
On Sat,
Sorry, took a while until I got time to test the changes. WIth the
current trunk revision I now can use restart exceptons within
onRequestHandlerExecuted to force a redirect to an error page and even
adding feedback messages seems to work properly.
Thank you very much for this fix! :-)
The
On Sun, Oct 16, 2011 at 1:51 AM, Kent Tong k...@cpttm.org.mo wrote:
Hi,
In 1.5, the request cycle (indirectly) contains a stack of request handlers.
According to the Java docs, it seems the purpose is to allow a request
handler to execute another request handler in its respond() method by
Hi Igor,
Thanks for the reply!
the usecase is simple, one requesthandler handing work off to another
one. an easy example is a request handler that handles a callback
(such as a link being clicked) scheduling the handler that renders the
page after it handled the click.
Yes, it is very
