The failover-manager-class Element"
From Documentation
m (Created page with '{{ZKConfigurationReferencePageHeader}} =Version History= {{LastUpdated}} {| border='1px' | width="100%" ! Version !! Date !! Content |- | | | |} {{ZKConfig…') |
m |
||
Line 1: | Line 1: | ||
{{ZKConfigurationReferencePageHeader}} | {{ZKConfigurationReferencePageHeader}} | ||
+ | |||
+ | '''Syntax:''' | ||
+ | <failover-manager-class>''a_class_name''</failover-manager-class> | ||
+ | |||
+ | [Default: ''none''] | ||
+ | |||
+ | It specifies which class used to handle the failover. It is called to recover a desktop, when ZK cannot locate a 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. | ||
=Version History= | =Version History= |
Revision as of 15:26, 4 December 2010
Syntax:
<failover-manager-class>a_class_name</failover-manager-class>
[Default: none]
It specifies which class used to handle the failover. It is called to recover a desktop, when ZK cannot locate a 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 |
---|---|---|