i added an enhancement request for next wicket version to support the
inspector better. the problem i'm having with it right now is that after
visiting the inspectorpage, every request to the web app results in a page
expired exception. the app is basically dead. has anyone seen this type of
behavior before (in the inspector or elsewhere)? any ideas on what this
might be? thanks!
jonathan
--
View this message in context:
http://www.nabble.com/inspector-causes-page-expired-tf3944109.html#a11188069
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
