Examples of org.zkoss.zk.ui.sys.FailoverManager

org.zkoss.zk.ui.sys.FailoverManager

Represents a class that is able to handle fail-over in the application specific way.

Desktops, pages and components are serializables, so you can use the clustering feature supported by the Web server without implementing this interface. In other words, you need to implement this interface only if you want to provide an application-specific way to re-create back.

If you want to use the Web server's clustering feature, what you need to do is to specify {@link org.zkoss.zk.ui.http.SerializableUiFactory}as the UI factory in zk.xml as follows (and forget {@link FailoverManager}).

 <system-config> <ui-factory-class>org.zkoss.zk.ui.http.SerializableUiFactory</ui-factory-class> </system-config>

The recovery involves two phases:

{@link #isRecoverable}: It tests whether the desktop is recoverable.
{@link #recover}: If recoverable, ZK will create the desktop accordingly, prepare the execution and then invoke this method to do real recovery.

@author tomyeh

   * @since 5.0.3
   */
  protected Desktop recoverDesktop(Session sess,
  HttpServletRequest request, HttpServletResponse response,
  WebAppCtrl wappc, String dtid) {
    final FailoverManager failover = wappc.getFailoverManager();
    if (failover != null) {
      Desktop desktop = null;
      try {
        if (failover.isRecoverable(sess, dtid)) {
          desktop = WebManager.getWebManager(_ctx)
            .getDesktop(sess, request, response, null, true);
          if (desktop == null) //forward or redirect
            throw new IllegalStateException("sendRediect or forward not allowed in recovering");

Examples of org.zkoss.zk.ui.sys.FailoverManager

Related Classes of org.zkoss.zk.ui.sys.FailoverManager