The org.zkoss.zk.ui.util.ExecutionInit interface"
m |
|||
Line 6: | Line 6: | ||
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. | ||
− | 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 the 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. |
'''Tip''': Executions might be stacked. To know whether it is the first execution since a (Servlet) request is processed, you can check whether the <tt>parent</tt> argument is <tt>null</tt>. | '''Tip''': Executions might be stacked. To know whether it is the first execution since a (Servlet) request is processed, you can check whether the <tt>parent</tt> argument is <tt>null</tt>. |
Revision as of 02:06, 8 August 2011
Listener:
org.zkoss.zk.ui.util.ExecutionInit
A listener could implement ExecutionInit to initialize a new execution.
When the 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.
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.