Just a thought which I did not think about when implementing this (thus I had
to change this stuff all over afterwards), perhaps it helps someone avoiding
the same mistake:
The latest rendered page is not neccessarily the page that lead the user to
the current page.
I.e. retrieving the last page this way might result in strange behavior if
the user uses two browser windows or tabs simulaneously. Same applies for
clicking the browser's back button.
Thus I had to go back to a rather old-fashioned solution, where every link
hands over a page param :-/ like in the good old days ;-)
rolandpeng wrote:
>
> great! after delare a ineer class below:
> class PageIdVersion {
> public int id;
> public int version;
> public PageIdVersion last;
> }
> then the track function works.
>
>
> John Patterson wrote:
>>
>>
>> // must declare hash map because meta data must be serializable
>> private MetaDataKey<HashMap<String, PageIdVersion>> lastPageIdVersionKey
>> = new MetaDataKey<HashMap<String, PageIdVersion>>() {};
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Possible-to-retrieve-previous-page-from-PageMap-tp20861106p22492628.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
