The org.zkoss.zk.ui.util.UiLifeCycle interface"
From Documentation
m |
m |
||
| Line 4: | Line 4: | ||
org.zkoss.zk.ui.util.UiLifeCycle | org.zkoss.zk.ui.util.UiLifeCycle | ||
| − | A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.UiLifeCycle</javadoc> to handle something depending on the life cycle of UI, such as attaching a component to a page, moving a component and so on | + | A listener could implement <javadoc type="interface">org.zkoss.zk.ui.util.UiLifeCycle</javadoc> to handle something depending on the life cycle of UI, such as attaching a component to a page, moving a component and so on. |
| − | + | '''Instantiation:''' | |
| + | For better performance, a single instance of the given class is instantiated when registered. It is then shared in the whole application. Thus, the implementation must be thread safe. | ||
| + | |||
| + | {{ZKConfigurationReferencePageFooter}} | ||
Latest revision as of 08:05, 21 April 2011
Listener:
org.zkoss.zk.ui.util.UiLifeCycle
A listener could implement UiLifeCycle to handle something depending on the life cycle of UI, such as attaching a component to a page, moving a component and so on.
Instantiation: For better performance, a single instance of the given class is instantiated when registered. It is then shared in the whole application. Thus, the implementation must be thread safe.