Event Threads

This documentation is for an older version of ZK. For the latest one, please click here.

By default, ZK processes an event in an independent thread called the event processing thread. Thus, the developer can suspend and resume the execution at any time, without blocking the servlet thread from sending back the responses to the browser.

However, it consumes more memory, especially if there are a lot suspended threads, and it may cause some challenge to integrate with other systems that storing information at the Servlet thread's local storage.

ZK provides an option to let you disable the use of the event processing threads. In other words, you can force ZK to process events all in the Servlet threads like other conventional frameworks. Of course, you cannot suspend the execution if the Servlet thread is used.

To disable the use of the event processing threads, you have to specify the following content in WEB-INF/zk.xml.

<system-config>
    <disable-event-thread/>
</system-config>

Here is the advantages and limitations about using the Servlet thread to process events. In the following sections we will talk more about the limitations and workarounds when using the Servlet thread.

	Using Servlet Thread	Using Event Processing Thread
Integration	Less integration issues. Many containers assume the HTTP request is handled in the servlet thread.	You may have to implement EventThreadInit and/or EventThreadCleanup to solve the integration issue. ZK and the community keep providing versatile implementations to solve the integration issue.
SuspendResume	No way to suspend the execution of the event listener. For example, you cannot create a modal window.	No limitation at all.

Modal Windows

You can not use the modal window anymore. You can create the same visual effect with the highlighted mode. However, at the server side, it works just like the overlapped mode – it returns immediately without waiting for user's response.

 win.doHighlighted(); //returns once the mode is changed; not suspended

Message Boxes

The message boxes returns immediately so it always returns Messagebox.OK. Thus, it is meaningless to show buttons other than the OK button. For example, the if clause in the following example is never true.

 if (Messagebox.show("Delete?", "Prompt", Messagebox.YES|Messagebox.NO,
     Messagebox.QUESTION) == Messagebox.YES) {
     this_never_executes();
 }

Rather, you have to provide an event listener as follows.

 Messagebox.show("Delete?", "Prompt", Messagebox.YES|Messagebox.NO,
     Messagebox.QUESTION,
     new EventListener() {
         public void onEvent(Event evt) {
             switch (((Integer)evt.getData()).intValue()) {
             case Messagebox.YES: doYes(); break; //the Yes button is pressed
             case Messagebox.NO: doNo(); break; //the No button is pressed
             }
         }
     }
 );

The event listener you provided is invoked when the user clicks one of the buttons. Then, you can identify which button is clicked by examining the data (Event's getData). The data is an integer whose value is the button's identifier, such as Messagebox.YES.

Alternatively, you can examine the event name:

 public void onEvent(Event evt) {
     if ("onYes".equals(evt.getName())) {
         doYes(); //the Yes button is pressed
     } else if ("onNo".equals(evt.getName())) {
         doNo(); //the No button is pressed
     }
 }

Note: The event name for the OK button is onOK, not onOk.

File Upload

The file upload dialog is no longer applicable. Rather, you shall use the fileupload component instead. The fileupload component is not a modal dialog. Rather, it is placed inline with other components. Refer to the fileupload Component section for more information.

<fileupload onUpload="handle(event)"/>