The org.zkoss.zk.ui.util.Initiator interface"
m |
m |
||
| Line 12: | Line 12: | ||
If you want to process only certain pages, you can check the request path by calling <javadoc method="getRequestPath()" type="interface">org.zkoss.zk.ui.Desktop</javadoc> (the desktop instance can be found thru the give component). | If you want to process only certain pages, you can check the request path by calling <javadoc method="getRequestPath()" type="interface">org.zkoss.zk.ui.Desktop</javadoc> (the desktop instance can be found thru the give component). | ||
| − | + | '''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}} | {{ZKConfigurationReferencePageFooter}} | ||
Revision as of 07:57, 21 April 2011
Listener:
org.zkoss.zk.ui.util.Initiator
[since 5.0.7]
A listener could implement Initiator to handle the initialization of a ZUML page, as if it is specified in the init directive. This kind of listeners is called system-level initiators.
Each time a ZK page is created, ZK will instantiate one instance for each registered system-level initiator and the invoke Initiator.doInit(Page, Map) and other methods.
If you want to process only certain pages, you can check the request path by calling Desktop.getRequestPath() (the desktop instance can be found thru the give component).
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.