Here is what I mean by rebuilds. For this instance I have a browse page and a viewDetails page, you click links on the browse page and it changes the contents on the browse page.(I've tried stateless and regular link). So lets say I hit the next link twice and then I hit the back button on my browser. So i hit next twice goes browse.0 -> browse.1 then browse.1->browse.2 then I hit back so then I'm once again on browse.1 now I place 2 debug breakpoints one in browse constructor and one in viewdetails constructor. I click a viewdetails link and the first thing it does is hit the browse constructor again rebuilding in other words re-constructing from the constructor keeping all data that was there when I left browse.2 and it rebuilds the browse page the way browse.2 was built because it has all the same data. So then the viewdetails link displays details for one of the vehicles that was on browse.2.
So as for dealing with a same instance, it is not, it is creating a new instance when I click a link on browse.1. I would rather that it clicks a link on the previous instance of browse.1 that i had(Is this what you were explaining as the way wicket should work?). Or anything else that would give the effect of clicking the back button and having the links displayed actually point to the details of that vehicle. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Another-back-button-issue-question-on-answer-given-in-another-thread-tp2266535p2267305.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
