Hi folks,

I know that there has been a lot of written about pagestores and
multi-window support in wicket 1.5, but i have several other
questions:

1. Is multi-window supported for non-versioned pages?

If page is versioned everything works ok, but i always get
StalePageExceptions when i use multiple windows/tabs with
non-versioned pages.
I think that StalePageException is useful in some cases when you wanna
be sure that user has same page in all windows, but in older versions
of wicket it was possible to have non versioned pages and multi-window
support together (e.g. we have an application written in wicket 1.2.6
that uses non-versioned pages in multiple windows)

2. How page stores work in clustered environment?

In older versions of wicket we used pagemaps stored in HttpSession.
When one node in cluster refuses to handle request, it was
successfully handled by another nod, because HttpSession was
replicated to another node. We have used non-versioned pages (no back
button support needed) and in one pagemap there was max 5 pages.
Wicket provided this functionality out-of-box.

3. How to achieve this in wicket 1.5?

I have found PersistentPageManager which uses IPageStore to store
pages. Pages are stored on disk by default, but there is also thread
safe SerializedPagesCache with SoftReferences. Theres no out-of-box
solution to store pages in HttpSession.

I have also found file page-management.txt in org.apache.wicket.page
package. It contains proposal of other pagamanagers and multi-window
support for non-versioned pages.

The proposal contains classes

PersistentPageManager with DiskPageStore and
SecondLevelCacheSessionStore for versioned pages
SessionManager for holding non versioned pages in HttpSession.

4. Can we expect that this proposal will be implemented in wicket 1.5
final version?

Thanks for your replies.

BR,
Michal Kurtak

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to