The org.zkoss.zk.ui.util.ExecutionInit interface"
From Documentation
m |
m |
||
| Line 2: | Line 2: | ||
'''Listener:''' | '''Listener:''' | ||
| − | org.zkoss.zk.ui.util.ExecutionInit | + | org.zkoss.zk.ui.util.ExecutionInit |
A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.ExecutionInit</javadoc> to initialize a new execution. | A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.ExecutionInit</javadoc> to initialize a new execution. | ||
| Line 13: | Line 13: | ||
| − | + | {{ZKConfigurationReferencePageFooter}} | |
Revision as of 06:17, 20 April 2011
Listener:
org.zkoss.zk.ui.util.ExecutionInit
A listener could implement ExecutionInit to initialize a new execution.
When ZK Loader and Update Engine created a new execution, it invokes the init method of this interface such that developers could plug the application-specific codes to initialize an execution.
Tip: Executions might be stacked. To know whether it is the first execution since a (Servlet) request is processed, you can check whether the parent argument is null.
A developer can prevent an execution from being created by throwing an exception in the init method.