The org.zkoss.zk.ui.util.ExecutionInit interface"
From Documentation
m |
|||
| Line 1: | Line 1: | ||
{{ZKConfigurationReferencePageHeader}} | {{ZKConfigurationReferencePageHeader}} | ||
| − | ''' | + | |
| + | '''Listener:''' | ||
org.zkoss.zk.ui.util.ExecutionInit interface | org.zkoss.zk.ui.util.ExecutionInit interface | ||
| − | <javadoc type="interface">org.zkoss.zk.ui.util.ExecutionInit</javadoc> | + | A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.ExecutionInit</javadoc> to initialize a new execution. |
When ZK Loader and Update Engine created a new execution, it invokes the <tt>init</tt> method of this interface such that developers could plug the application-specific codes to initialize an execution. | When ZK Loader and Update Engine created a new execution, it invokes the <tt>init</tt> method of this interface such that developers could plug the application-specific codes to initialize an execution. | ||
Revision as of 06:14, 20 April 2011
Listener:
org.zkoss.zk.ui.util.ExecutionInit interface
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.