|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
java.lang.Objectorg.zkoss.zkplus.databind.AnnotateDataBinderInit
public class AnnotateDataBinderInit
This initiator class do following things:
AnnotateDataBinder instance.DataBinder.loadAll() in to doAfterCompose(Page, Component[]) and
initiate all UI components from the associated data bean.Put the init PI as follows:
<?init class="org.zkoss.zkplus.databind.AnnotateDataBinderInit"
[root="component|component-path"]
[loadDefault="true|false"]
[name="binder's name"]
[loadOnSave="true|false"] ?>
Where the root attribute is the component itself (via EL expression) or the component path that specifies the component the AnnotateDataBinder covers. You can use absolute path that starts with "//" (search from Desktop) or "/" (search from Page); or you can use relative path(supported since ZK 3.0.8) that starts with "./" or "../" (relative to the Id Space of the root component). If the root attribute is not specified or set to string "page", the AnnotateDataBinder will default to cover the whole page.
Where the loadDefault attribute is used to decide whether to load default binding configuration defined in lang-addon.xml. If the loadDefault attribute is not specified it is default to true.
(since 3.6.2) Where the name attribute is used to specify the created DataBinder's name (default to "binder") which you can access it via EL or component.getAttribute(name) later.
(since 5.0.5) Where the loadOnSave attribute(default to true) is used to specify whether DataBinder shall automatically "load" associated binding value back into UI component after doing a "save" operation to the binding bean.
For application design to run ZK prior to 3.6.2, it can use arg0 instead of root, and arg1 instead of loadDefault.
Note that since 5.0, the created DataBinder is stored in component scope of the root component rather than in the IdSpace scope of the root component. If that is important to you, you can specify compatible library property in WEB-INF/zk.xml to true to make it work as it was prior version 5; i.e. store the created DataBinder in IdSpace scope of the root component.
<library-property>
<name>org.zkoss.zkplus.databind.AnnotateDataBinderInit.compatible</name>
<value>true</value>
</library-property>
AnnotateDataBinder| Field Summary | |
|---|---|
protected AnnotateDataBinder |
_binder
Deprecated. The AnnotateDataBinder created in doAfterCompose() |
| Constructor Summary | |
|---|---|
AnnotateDataBinderInit()
Deprecated. |
|
| Method Summary | |
|---|---|
void |
doAfterCompose(org.zkoss.zk.ui.Page page,
org.zkoss.zk.ui.Component[] comps)
Deprecated. |
boolean |
doCatch(Throwable ex)
Deprecated. |
void |
doFinally()
Deprecated. |
void |
doInit(org.zkoss.zk.ui.Page page,
Map args)
Deprecated. |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Field Detail |
|---|
protected AnnotateDataBinder _binder
| Constructor Detail |
|---|
public AnnotateDataBinderInit()
| Method Detail |
|---|
public boolean doCatch(Throwable ex)
doCatch in interface org.zkoss.zk.ui.util.InitiatorExtpublic void doFinally()
doFinally in interface org.zkoss.zk.ui.util.InitiatorExt
public void doInit(org.zkoss.zk.ui.Page page,
Map args)
doInit in interface org.zkoss.zk.ui.util.Initiator
public void doAfterCompose(org.zkoss.zk.ui.Page page,
org.zkoss.zk.ui.Component[] comps)
throws Exception
doAfterCompose in interface org.zkoss.zk.ui.util.InitiatorExtException
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||