Re: Question regarding navigation with the browser's back button
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 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 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, 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 internal error. Is there anyway to make the Java web page to be regenerated, instead of using the previous one? So that the tree is re-drawn without the item. ( in the address bar the url ends with :4::. after deleting it becomes :5::, but when I press the back button, the :4:: appears, and so does the internal error. any ideas on how to make it re-draw the tree, using real data? Chris On 11/5/07, Igor Vaynberg [EMAIL PROTECTED] wrote: 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 issues in the list, but couldn't find any to solve my problem. I have a page that show a Tree with many items. These items can be deleted using a link. When the item is deleted the page is reloaded using SetResponsePage(). Then if I click the browser's back button, I go to the previous page in which this item was not deleted, causing an inconsistence between the tree and the real thing, that will eventually cause an internal error leading the user to the internal error page. Is there a way to tell wicket that if the back button is pressed, to reload the page fully, i.e. rebuild it, not using cache? Thanks in advanced, Chris - 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]
Re: Question regarding navigation with the browser's back button
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 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, 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 internal error. Is there anyway to make the Java web page to be regenerated, instead of using the previous one? So that the tree is re-drawn without the item. ( in the address bar the url ends with :4::. after deleting it becomes :5::, but when I press the back button, the :4:: appears, and so does the internal error. any ideas on how to make it re-draw the tree, using real data? Chris On 11/5/07, Igor Vaynberg [EMAIL PROTECTED] wrote: 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 issues in the list, but couldn't find any to solve my problem. I have a page that show a Tree with many items. These items can be deleted using a link. When the item is deleted the page is reloaded using SetResponsePage(). Then if I click the browser's back button, I go to the previous page in which this item was not deleted, causing an inconsistence between the tree and the real thing, that will eventually cause an internal error leading the user to the internal error page. Is there a way to tell wicket that if the back button is pressed, to reload the page fully, i.e. rebuild it, not using cache? Thanks in advanced, Chris - 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]
Re: Question regarding navigation with the browser's back button
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 issues in the list, but couldn't find any to solve my problem. I have a page that show a Tree with many items. These items can be deleted using a link. When the item is deleted the page is reloaded using SetResponsePage(). Then if I click the browser's back button, I go to the previous page in which this item was not deleted, causing an inconsistence between the tree and the real thing, that will eventually cause an internal error leading the user to the internal error page. Is there a way to tell wicket that if the back button is pressed, to reload the page fully, i.e. rebuild it, not using cache? Thanks in advanced, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Question regarding navigation with the browser's back button
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 internal error. Is there anyway to make the Java web page to be regenerated, instead of using the previous one? So that the tree is re-drawn without the item. ( in the address bar the url ends with :4::. after deleting it becomes :5::, but when I press the back button, the :4:: appears, and so does the internal error. any ideas on how to make it re-draw the tree, using real data? Chris On 11/5/07, Igor Vaynberg [EMAIL PROTECTED] wrote: 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 issues in the list, but couldn't find any to solve my problem. I have a page that show a Tree with many items. These items can be deleted using a link. When the item is deleted the page is reloaded using SetResponsePage(). Then if I click the browser's back button, I go to the previous page in which this item was not deleted, causing an inconsistence between the tree and the real thing, that will eventually cause an internal error leading the user to the internal error page. Is there a way to tell wicket that if the back button is pressed, to reload the page fully, i.e. rebuild it, not using cache? Thanks in advanced, Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Question regarding navigation with the browser's back button
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, 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 internal error. Is there anyway to make the Java web page to be regenerated, instead of using the previous one? So that the tree is re-drawn without the item. ( in the address bar the url ends with :4::. after deleting it becomes :5::, but when I press the back button, the :4:: appears, and so does the internal error. any ideas on how to make it re-draw the tree, using real data? Chris On 11/5/07, Igor Vaynberg [EMAIL PROTECTED] wrote: 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 issues in the list, but couldn't find any to solve my problem. I have a page that show a Tree with many items. These items can be deleted using a link. When the item is deleted the page is reloaded using SetResponsePage(). Then if I click the browser's back button, I go to the previous page in which this item was not deleted, causing an inconsistence between the tree and the real thing, that will eventually cause an internal error leading the user to the internal error page. Is there a way to tell wicket that if the back button is pressed, to reload the page fully, i.e. rebuild it, not using cache? Thanks in advanced, Chris - 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]
