What do you mean by "rebuilds"? Wicket is designed so that links (non-bookmarkable ones at least) will always "point" back at the page from whence they came, so that their state remains consistent. So, if you mean that the link seems to be dealing with the same page instance that it came from, then that's how it's supposed to work.
On Thu, Jun 24, 2010 at 2:34 AM, Boneless1213 <boneless1...@gmail.com> wrote: > > Hello, I fixed a previous problem I had with a back button that I described > as unlike the other back button issues. This time it is more like the other > back button issues, and I wonder about this post made by another person in > this thread > http://apache-wicket.1842946.n4.nabble.com/wicket-back-button-problem-td1912501.html#a1912501 > http://apache-wicket.1842946.n4.nabble.com/wicket-back-button-problem-td1912501.html#a1912501 > > I'm experiencing the problem where you hit the back button click on a link > and it's like it hit the link on the other page instead of the one you are > on. > > When I click a link it seems to rebuild the page instead of any undoing, > There is obviously something I don't understand about the undo > functionality. When it rebuilds it obviously has all the same data as I had > before and rebuilds based on that data. I don't expect it to undo all of my > fields on my class I realize that is ridiculous, how I understood the > comment in that thread is that it replaces your components with older > versions while I see through debugging that it rebuilds the view. Otherwise > I suppose I would store the data on the component class(Such as add a field > to my link and have it link there). > > I'll be happy to hear any advice on the issue I'm having even if it has > nothing to do with the post I referenced. Thank you very much. > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Another-back-button-issue-question-on-answer-given-in-another-thread-tp2266535p2266535.html > Sent from the Wicket - Dev mailing list archive at Nabble.com. >
