ZK Configuration"
From Documentation
m |
|||
| Line 10: | Line 10: | ||
</zk> | </zk> | ||
</source> | </source> | ||
| + | |||
| + | <javadoc>org.zkoss.zk.ui.http.SerializableUiFactory</javadoc> is the UI factory that will instantiate serializable sessions such that the sessions, components, pages and desktops will be serialized when a session is about to deactivate. | ||
Also notice that you cannot enable the use of the event thread<ref>The reason is that the event thread might be suspended. Unfortunately, the thread cannot be migrated from one machine to another.</ref>. It is disabled by default. For more information, please refer to the [[ZK Developer's Reference/UI Patterns/Event Threads|Event Threads]] section. | Also notice that you cannot enable the use of the event thread<ref>The reason is that the event thread might be suspended. Unfortunately, the thread cannot be migrated from one machine to another.</ref>. It is disabled by default. For more information, please refer to the [[ZK Developer's Reference/UI Patterns/Event Threads|Event Threads]] section. | ||
Revision as of 03:37, 18 November 2010
To use ZK in a clustering environment, you have to use the serializable UI factory. It could be done by specifying the following statement in WEB-INF/zk.xml:
<zk>
<system-config>
<ui-factory-class>org.zkoss.zk.ui.http.SerializableUiFactory</ui-factory-class>
</system-config>
</zk>
SerializableUiFactory is the UI factory that will instantiate serializable sessions such that the sessions, components, pages and desktops will be serialized when a session is about to deactivate.
Also notice that you cannot enable the use of the event thread[1]. It is disabled by default. For more information, please refer to the Event Threads section.
- ↑ The reason is that the event thread might be suspended. Unfortunately, the thread cannot be migrated from one machine to another.
Version History
| Version | Date | Content |
|---|---|---|