If it is related to back button, it's probably browser caching wrong page version. E.g. you have a panel on page, then remove it (through ajax) and go to another page. When you return back, the page in browser cache may contain the panel (which is already removed on serverside).
Unfortunately there is only one solution for this - adding cache-control:no-store header to force browser reload page on back button. -Matej On Dec 18, 2007 11:07 PM, Doug Leeper <[EMAIL PROTECTED]> wrote: > > I have been seeing something similar. Since it is not consistent, I can't > pin down the cause or create a test case for this. I will keep plugging > along and try to pin point it. > > However, I do know that happens when I go back to a page that has been > already shown. Other than that, I can't say much. > -- > View this message in context: > http://www.nabble.com/Component-not-found-on-Page-Error-tp14401739p14406692.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
