01: /*
02: * ==============================================================================
03: * Licensed under the Apache License, Version 2.0 (the "License"); you may not
04: * use this file except in compliance with the License. You may obtain a copy of
05: * the License at
06: *
07: * http://www.apache.org/licenses/LICENSE-2.0
08: *
09: * Unless required by applicable law or agreed to in writing, software
10: * distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
11: * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
12: * License for the specific language governing permissions and limitations under
13: * the License.
14: */
15: package wicket.jmx;
16:
17: import wicket.markup.html.WebPage;
18:
19: /**
20: * Page settings.
21: *
22: * @author eelcohillenius
23: */
24: public interface PageSettingsMBean {
25: /**
26: * Gets whether Wicket should try to support opening multiple windows for
27: * the same session transparently. If this is true - the default setting -,
28: * Wicket tries to detect whether a new window was opened by a user (e.g. in
29: * Internet Explorer by pressing ctrl+n or ctrl+click on a link), and if it
30: * detects that, it creates a new page map for that window on the fly. As a
31: * page map represents the 'history' of one window, each window will then
32: * have their own history. If two windows would share the same page map, the
33: * non-bookmarkable links on one window could refer to stale state after
34: * working a while in the other window.
35: * <p>
36: * <strong> Currently, Wicket trying to do this is a best effort that is not
37: * completely fail safe. When the client does not support cookies, support
38: * gets tricky and incomplete. See {@link WebPage}'s internals for the
39: * implementation. </strong>
40: * </p>
41: *
42: * @return Whether Wicket should try to support multiple windows
43: * transparently
44: */
45: boolean getAutomaticMultiWindowSupport();
46:
47: /**
48: * @return Returns the maxPageVersions.
49: */
50: int getMaxPageVersions();
51:
52: /**
53: * @return Returns the pagesVersionedByDefault.
54: */
55: boolean getVersionPagesByDefault();
56:
57: /**
58: * Sets whether Wicket should try to support opening multiple windows for
59: * the same session transparently. If this is true - the default setting -,
60: * Wicket tries to detect whether a new window was opened by a user (e.g. in
61: * Internet Explorer by pressing ctrl+n or ctrl+click on a link), and if it
62: * detects that, it creates a new page map for that window on the fly. As a
63: * page map represents the 'history' of one window, each window will then
64: * have their own history. If two windows would share the same page map, the
65: * non-bookmarkable links on one window could refer to stale state after
66: * working a while in the other window.
67: * <p>
68: * <strong> Currently, Wicket trying to do this is a best effort that is not
69: * completely fail safe. When the client does not support cookies, support
70: * gets tricky and incomplete. See {@link WebPage}'s internals for the
71: * implementation. </strong>
72: * </p>
73: *
74: * @param automaticMultiWindowSupport
75: * Whether Wicket should try to support multiple windows
76: * transparently
77: */
78: void setAutomaticMultiWindowSupport(
79: boolean automaticMultiWindowSupport);
80:
81: /**
82: * @param maxPageVersions
83: * The maxPageVersion to set.
84: */
85: void setMaxPageVersions(int maxPageVersions);
86:
87: /**
88: * @param pagesVersionedByDefault
89: * The pagesVersionedByDefault to set.
90: */
91: void setVersionPagesByDefault(boolean pagesVersionedByDefault);
92: }
|