The org.zkoss.zk.ui.util.ExecutionCleanup interface"
From Documentation
m |
m (correct highlight (via JWB)) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 6: | Line 6: | ||
A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.ExecutionCleanup</javadoc> to cleanup an execution that is being destroyed. | A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.ExecutionCleanup</javadoc> to cleanup an execution that is being destroyed. | ||
| − | When ZK Loader is going to destroy an execution, it invokes the < | + | 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
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.