| org.apache.wicket.settings.IPageSettings
All known Subclasses: org.apache.wicket.settings.Settings,
| IPageSettings | | public interface IPageSettings (Code) | | Interface for page related settings.
author:
Igor Vaynberg (ivaynberg)
author:
Eelco Hillenius |
| getAutomaticMultiWindowSupport | | boolean getAutomaticMultiWindowSupport()(Code) | | 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.
Whether Wicket should try to support multiple windowstransparently |
| getComponentResolvers | | List getComponentResolvers()(Code) | | Get the (modifiable) list of IComponentResolvers.
See Also: AutoComponentResolver
See Also: for an example List of ComponentResolvers |
| getVersionPagesByDefault | | boolean getVersionPagesByDefault()(Code) | | Returns the pagesVersionedByDefault. |
| setAutomaticMultiWindowSupport | | void setAutomaticMultiWindowSupport(boolean automaticMultiWindowSupport)(Code) | | 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 windowstransparently |
| setVersionPagesByDefault | | void setVersionPagesByDefault(boolean pagesVersionedByDefault)(Code) | |
Parameters:
pagesVersionedByDefault - The pagesVersionedByDefault to set. |
|
|