a good start is to isolate this in a quickstart so we can all look at it. if
you want to do it yourself then just break in request cycle and walk the
steps, see why the page cannot be resolved.
-igor
On 1/16/07, Ryan Sonnek <[EMAIL PROTECTED]> wrote:
I'm running wicket-2.0 from a recent svn checkout and i'm seeing a *lot*
of page expired exceptions when using ajax behaviors. I'm wondering where I
can start digging to see why this is happening. Any ideas?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user