no not yet. the request processing is not procedural, it relies heavily on polymorphism. so im not sure if a simple diagram like that can be created to represent it. so far we just havent had the time.

if you are really interested
RequestCycle.steps()
and
RequestCycle.step()
are good places to start looking

-Igor



On 2/21/06, Piotr Bzdyl < [EMAIL PROTECTED]> wrote:
Hello,
> when a url is accessed for a page that cannot be found in the pagemap
> it is considered an expired page.
>
> so basically you create a page, some time passes and that page is
> removed from the pagemap via the page eviction strategy. so if you go
> back to that page and click a link, that url will try to retrieve the
> page from the pagemap, and since the page cannot be found you get the
> page expired page.
>
> you can set your own via
> Application.getApplicationSettings().setPageExpiredErrorPage()
Is there any diagram showing how requests are processed? How looks flow
control etc? Something similar to
http://piotr.radzisz.com/sample-diagram.png. This would help to
understand how wicket works.

Best regards,
Piotr


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to