we already have session unique pageid's: getApplication().getSessionSettings().isPageIdUniquePerSession()
Then you dont have to have pagemap or enable the multi window support You only need that if you really want to now that users uses different tabs. Wicket doesnt really need it anymore then Because it will find the pages in the diskstore by there id's just fine (as long as your diskstore is large enough for the default pagemap) johan On Mon, Jul 13, 2009 at 19:07, Igor Vaynberg <igor.vaynb...@gmail.com>wrote: > not sure if storing in a cookie would work easily. we would still have > to keep the cookie name somewhere...and so you are back to adding that > to the url. > > i think in 1.5 what we can do is make the page id unique across all > pagemaps and keep the mapping in session. not sure how easy that would > be to implement in 1.4. > > -igor > > On Mon, Jul 13, 2009 at 4:30 AM, Oliver Krohne<okro...@yahoo.de> wrote: > > Hi, > > > > I turned on the option Automatic Multi Window Support and now if I open > some > > windows / tabs I see the pagemap name in the url like > "/?wicket:pageMapName=wicket-3". > > After each link I click the pagemap name changes even in the same window, > I wonder if > > this is correct ? > > > > Is there any way that the pagemap does not appear in the url? > > Could it be stored in a cookie? > > > > A part of my website is displayed in an iframe on some customer pages. If > a user opens pages > > in the iframe and then switches to the main website possibly in a > different window then sometimes > > I got PageExpiredException . > > Is there a way to force all iframed pages to use a different pagemap > without displaying the pagemap name > > in the url on the main (non iframed) website? > > > > > > Thanks for any hints, > > > > Oliver > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
