wicket.jmx
Interface PageSettingsMBean

All Known Implementing Classes:

PageSettings

public interface PageSettingsMBean

Page settings.

Author:

eelcohillenius

Method Summary

boolean	getAutomaticMultiWindowSupport() Gets whether Wicket should try to support opening multiple windows for the same session transparently.
int	getMaxPageVersions()
boolean	getVersionPagesByDefault()
void	setAutomaticMultiWindowSupport(boolean automaticMultiWindowSupport) Sets whether Wicket should try to support opening multiple windows for the same session transparently.
void	setMaxPageVersions(int maxPageVersions)
void	setVersionPagesByDefault(boolean pagesVersionedByDefault)

Method Detail

getAutomaticMultiWindowSupport

boolean getAutomaticMultiWindowSupport()

Gets whether Wicket should try to support opening multiple windows for the same session transparently. If this is true - the default setting -, Wicket tries to detect whether a new window was opened by a user (e.g. in Internet Explorer by pressing ctrl+n or ctrl+click on a link), and if it detects that, it creates a new page map for that window on the fly. As a page map represents the 'history' of one window, each window will then have their own history. If two windows would share the same page map, the non-bookmarkable links on one window could refer to stale state after working a while in the other window.

Currently, Wicket trying to do this is a best effort that is not completely fail safe. When the client does not support cookies, support gets tricky and incomplete. See WebPage's internals for the implementation.

Returns:

Whether Wicket should try to support multiple windows transparently

getMaxPageVersions

int getMaxPageVersions()

Returns:

Returns the maxPageVersions.

getVersionPagesByDefault

boolean getVersionPagesByDefault()

Returns:

Returns the pagesVersionedByDefault.

setAutomaticMultiWindowSupport

void setAutomaticMultiWindowSupport(boolean automaticMultiWindowSupport)

Sets whether Wicket should try to support opening multiple windows for the same session transparently. If this is true - the default setting -, Wicket tries to detect whether a new window was opened by a user (e.g. in Internet Explorer by pressing ctrl+n or ctrl+click on a link), and if it detects that, it creates a new page map for that window on the fly. As a page map represents the 'history' of one window, each window will then have their own history. If two windows would share the same page map, the non-bookmarkable links on one window could refer to stale state after working a while in the other window.

Currently, Wicket trying to do this is a best effort that is not completely fail safe. When the client does not support cookies, support gets tricky and incomplete. See WebPage's internals for the implementation.

Parameters:

automaticMultiWindowSupport - Whether Wicket should try to support multiple windows transparently

setMaxPageVersions

void setMaxPageVersions(int maxPageVersions)

Parameters:

maxPageVersions - The maxPageVersion to set.

setVersionPagesByDefault

void setVersionPagesByDefault(boolean pagesVersionedByDefault)

Parameters:

pagesVersionedByDefault - The pagesVersionedByDefault to set.