The org.zkoss.zk.ui.util.ExecutionCleanup interface"

From Documentation
m (correct highlight (via JWB))
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
  {{ZKConfigurationReferencePageHeader}}
 
  {{ZKConfigurationReferencePageHeader}}
'''Property:'''
 
org.zkoss.zk.ui.util.ExecutionCleanup interface
 
  
<javadoc type="interface">org.zkoss.zk.ui.util.ExecutionCleanup</javadoc> is implemented by a listener class that will be used to cleanup an execution that is being destroyed.
+
'''Listener:'''
 +
org.zkoss.zk.ui.util.ExecutionCleanup
  
When ZK Loader is going to destroy an execution, it invokes the <tt>cleanup</tt> method of this interface such that developers could plug the application-specific codes to cleanup an execution.
+
A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.ExecutionCleanup</javadoc> to cleanup an execution that is being destroyed.
  
{{ZKConfigurationReferencePageFooter}}
+
When ZK Loader is going to destroy an execution, it invokes the <code>cleanup</code> method of this interface such that developers could plug the application-specific codes to cleanup an execution.
 +
 
 +
'''Instantiation:'''
 +
An independent instance of the given class is instantiated each time before the method is invoked. It means it is thread safe, and all information stored in non-static members will be lost after called.
 +
 
 +
{{ZKConfigurationReferencePageFooter}}

Latest revision as of 10:33, 19 January 2022


DocumentationZK Configuration Referencezk.xmlThe listener ElementThe org.zkoss.zk.ui.util.ExecutionCleanup interface
The org.zkoss.zk.ui.util.ExecutionCleanup interface


Listener:

org.zkoss.zk.ui.util.ExecutionCleanup

A listener could implement ExecutionCleanup to cleanup an execution that is being destroyed.

When ZK Loader is going to destroy an execution, it invokes the cleanup method of this interface such that developers could plug the application-specific codes to cleanup an execution.

Instantiation: An independent instance of the given class is instantiated each time before the method is invoked. It means it is thread safe, and all information stored in non-static members will be lost after called.



Last Update : 2022/01/19

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.