The failover-manager-class Element"
From Documentation
m |
|||
| Line 6: | Line 6: | ||
[Default: ''none''] | [Default: ''none''] | ||
| − | It specifies which class used to handle the failover. | + | It specifies which class should be used to handle the failover. This is called to recover a desktop, when ZK cannot locate the desktop. The class must have a default constructor (without any argument), and implement the <javadoc type="interface">org.zkoss.zk.ui.sys.FailoverManager</javadoc> interface. |
In most cases, you don't need to provide any implementation. Rather, you can let Web servers to handle failover and clustering for you by specifying the <javadoc>org.zkoss.zk.ui.http.SerializableUiFactory</javadoc> class in the <tt>ui-factory-class</tt> element as described above. | In most cases, you don't need to provide any implementation. Rather, you can let Web servers to handle failover and clustering for you by specifying the <javadoc>org.zkoss.zk.ui.http.SerializableUiFactory</javadoc> class in the <tt>ui-factory-class</tt> element as described above. | ||
Revision as of 03:44, 8 August 2011
Syntax:
<failover-manager-class>a_class_name</failover-manager-class>
[Default: none]
It specifies which class should be used to handle the failover. This is called to recover a desktop, when ZK cannot locate the desktop. The class must have a default constructor (without any argument), and implement the FailoverManager interface.
In most cases, you don't need to provide any implementation. Rather, you can let Web servers to handle failover and clustering for you by specifying the SerializableUiFactory class in the ui-factory-class element as described above.
Version History
| Version | Date | Content |
|---|---|---|