org.apache.wicket.settings
Interface IPageSettings

All Known Implementing Classes:

Settings

public interface IPageSettings

Interface for page related settings.

Author:

Igor Vaynberg (ivaynberg), Eelco Hillenius

Method Summary

void	addComponentResolver(IComponentResolver resolver) Adds a component resolver to the list.
boolean	getAutomaticMultiWindowSupport() Gets whether Wicket should try to support opening multiple windows for the same session transparently.
java.util.List	getComponentResolvers() Get the (modifiable) list of IComponentResolvers.
boolean	getVersionPagesByDefault()
void	setAutomaticMultiWindowSupport(boolean automaticMultiWindowSupport) Sets whether Wicket should try to support opening multiple windows for the same session transparently.
void	setVersionPagesByDefault(boolean pagesVersionedByDefault)

Method Detail

addComponentResolver

void addComponentResolver(IComponentResolver resolver)

Adds a component resolver to the list.

Parameters:

resolver - The IComponentResolver that is added

getComponentResolvers

java.util.List getComponentResolvers()

Get the (modifiable) list of IComponentResolvers.

Returns:

List of ComponentResolvers

See Also:

for an example

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

getVersionPagesByDefault

boolean getVersionPagesByDefault()

Returns:

Returns the pagesVersionedByDefault.

setVersionPagesByDefault

void setVersionPagesByDefault(boolean pagesVersionedByDefault)

Parameters:

pagesVersionedByDefault - The pagesVersionedByDefault to set.

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