UI Factory"
m ((via JWB)) |
RebeccaLai (talk | contribs) m |
||
Line 3: | Line 3: | ||
<javadoc type="interface">org.zkoss.zk.ui.sys.UiFactory</javadoc> is used to instantiate all UI objects, such as session, desktop, and components, and to load ZUML documents. You could customize it to provide the functionality you want. | <javadoc type="interface">org.zkoss.zk.ui.sys.UiFactory</javadoc> is used to instantiate all UI objects, such as session, desktop, and components, and to load ZUML documents. You could customize it to provide the functionality you want. | ||
− | For example, <javadoc>org.zkoss.zk.ui.http.SerializableUiFactory</javadoc> is the factory used to instantiate sessions that are serializable<ref>Then, the application is able to run in a clustering environment. | + | For example, <javadoc>org.zkoss.zk.ui.http.SerializableUiFactory</javadoc> is the factory used to instantiate sessions that are serializable<ref>Then, the application is able to run in a clustering environment. For more information, please refer to the [[ZK Developer's Reference/Clustering/ZK Configuration|Clustering section]]</ref>, while <javadoc>org.zkoss.zk.ui.http.SimpleUiFactory</javadoc>, the default factory, instantiates non-serializable sessions. |
Here are a list of customization you could do with UI Factory: | Here are a list of customization you could do with UI Factory: |
Revision as of 09:22, 2 February 2024
UiFactory is used to instantiate all UI objects, such as session, desktop, and components, and to load ZUML documents. You could customize it to provide the functionality you want.
For example, SerializableUiFactory is the factory used to instantiate sessions that are serializable[1], while SimpleUiFactory, the default factory, instantiates non-serializable sessions.
Here are a list of customization you could do with UI Factory:
- Load a ZUML document from, say, a database
- It can be done by overriding UiFactory.getPageDefinition(RequestInfo, String)
- Instantiate a component by using a different implementation
- It can be done by overriding UiFactory.newComponent(Page, Component, ComponentInfo) and UiFactory.newComponent(Page, Component, ComponentInfo, String).
- Instantiate a desktop by using a different implementation
- It can be done by overriding UiFactory.newDesktop(RequestInfo, String, String)
- Instantiate a page by using a different implementation
- It can be done by overriding UiFactory.newPage(RequestInfo, PageDefinition, String) and/or UiFactory.newPage(RequestInfo, Richlet, String)
Notice that it is suggested to extend from either SerializableUiFactory or SimpleUiFactory, rather than to implement UiFactory from scratch.
- ↑ Then, the application is able to run in a clustering environment. For more information, please refer to the Clustering section
Load ZUML from Database
The default implementation of AbstractUiFactory.getPageDefinition(RequestInfo, String) loads the ZUML document from the Web application's resources (i.e., the files found in a Web application). If you prefer to load from other sources, such as a database, you could override it.
The pseudo code will look like the following:
public class MyUiFactory extends SimpleUiFactory {
@Override
public PageDefinition getPageDefinition(RequestInfo ri, String path) {
PageDefinition pgdef = getFromCache(path); //your cache implementation
if (pgdef == null) {
String content = loadFromDatabase(path); //your resource loading
pgdef = getPageDefinition(ri, content, "zul"); //delegate to SimpleUiFactory
setCache(path, pgdef); //cache the result
}
return pgdef;
}
}
where we assume you implemented loadFromDatabase
to load the ZUML document from a database.
In addition, you have to implement getFromCache
and setCache
to cache the result in order to improve the performance of retrieving the document from the database.
On the other hand, the parsing of the ZUML document can be done easily by calling AbstractUiFactory.getPageDefinitionDirectly(RequestInfo, String, String).
Version History
Version | Date | Content |
---|---|---|