Page History

...

The first instance of home page with id 0 and version 0 was created when you went to application home page (i.e. typed in browser a URL like http://localhost:8080/app^{Image Removed}). Then after clicking on "gotoNewPage" link, page with id 1 and version 0 was created and added to the page map. Next two clicks on "changeState" link added to the page map versions 1 and 2 of the home page. And finally two clicks on "gotoNewPage" link created and added another two home page instances to the page map.

...

So for example to access second version of page instance with id 1 the following URL will be used: http://localhost:8080/app/?wicket:interface=:1:2:::^{Image Removed}. If there is no page with specified id and version, then "Page Expired" page will be shown.

Similarly components like Links and Buttons, which provide callback to user code, use URLs which point to the page instance in a page map. For example "changeState " link on the second version of page with id 1 will have URL like this http://localhost:8080/app/?wicket:interface=:1:changeState:2:ILinkListener::^{Image Removed} When this link is clicked Wicket will call onClick() handler for this link on the page instance with id 1 and version 2.

...

• on opening tab in web-browser (see IPageSettings#getAutomaticMultiWindowSupport())
• on creating modal/popup window
• when using inline frames
• anywhere in code using PageMap#forName() method
• it's not normal usecase, but page map is also created whenever a URL is requested which contains name of not-existing page map. For example URL like http://localhost:8080/app/?wicket:interface=newPageMap:0::::^{Image Removed} will create page map with name "newPageMap".

...