Another option - this might be a better first line of defence. Perhaps we
look at implementing the other solution if the problem still exists.
On Fri, Nov 9, 2007 at 2:42 AM, Christian Alejandro Marquez Grabia
[EMAIL PROTECTED] wrote:
Well...after trying on different things, what I did was
Well...after trying on different things, what I did was override the
onAttach method, and there I regenerate the tree.
Don't know if this is the better way, but it's working so far.
Thanks for your help,
Chris
On Nov 5, 2007 4:35 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
maybe your tree
override webpage#setheaders() and instead of no-cache set a no-store
header. that should force the browser to reload the page on
backbutton...
-igor
On 11/5/07, Christian Alejandro Marquez Grabia [EMAIL PROTECTED] wrote:
I am using Wicket version 1.2.6
I have been looking for this or related
Thanks Igor.
Indeed, the browser now reloads the page, but the Internal Error occurs now,
instead of watching the cached page. It seems that the Java page is
somewhere cached, and the tree is attempted to be reloaded, and since some
of the methods use the objects in the tree, it brings up the
maybe your tree model caches more then it should, not sure. if you
want regen the page then its url has to be bookmarkable, but the tree
doesnt work with that really without some extra work...
-igor
On 11/5/07, Christian Alejandro Marquez Grabia [EMAIL PROTECTED] wrote:
Thanks Igor.
Indeed,
