|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
java.lang.Objectorg.zkoss.zkplus.databind.DataBinder
org.zkoss.zkplus.databind.AnnotateDataBinder
public class AnnotateDataBinder
The DataBinder that reads ZUML annotations to create binding info. The ZUML page must declare the XML namespace, xmlns:a="http://www.zkoss.org/2005/zk/annotation", to use the ZUML annotations. The annotation is declared before each Component or specified directly on the Component attributes. For example, the following annotation associates the attibute "value" of the component "textbox" to the bean's value "person.address.city".
<a:bind value="person.address.city"/> <textbox/>
Or since ZK 2.4 you can annotate directly on the attribute "value" of the component "textbox" like this.
<textbox value="@{person.address.city}"/>
The @{...} pattern tells the ZUML parser that this is for annotation.
The AnnotateDataBinder knows "a:bind" annotation only. The complete format is like this if you declared it before the Component.
<a:bind attrY="bean's value;[tag:expression]..."/> <componentX/>
You can also specify directly on the Component attribute, the complete format is like this:
<componentX attrY="@{bean's value,[tag='expression']...}"/>
This associates the componentX's attribute attrY to the bean's value. The bean's value is something
in the form of beanid.field1.field2... You can either call DataBinder.bindBean(java.lang.String, java.lang.Object) to bind the beanid to a
real bean object or you can neglect it and this DataBinder would try to find it from the variables map via
(Component.getVariable(java.lang.String, boolean) method. That is, all those variables defined in zscript are
accessible by this DataBinder. Note that you can choose either two formats of annotaion as your will and you
can even hybrid them together though it is generaly not a good practice.
The tag:expression or tag='expression' is a generic form to bind more metainfo to the attrY of the componentX. The currently supported tag includes "load-when", "save-when", "access", and "converter"
Declare in front of the Component:
<a:bind value="person.firstName"/> <textbox id="firstname"/> <a:bind value="person.lastName"/> <textbox id="lastname"/> <a:bind value="person.fullName; load-when:firstname.onChange; load-when:lastname.onChange"/> <label id="fullname"/>
Or specify directly on the Component's attribute:
<textbox id="firstname" value="@{person.firstName}"/>
<textbox id="lastname" value="@{person.lastName}"/>
<label id="fullname" value="@{person.fullName, load-when='firstname.onChange,lastname.onChange'}"/>
Declare in front of the Component:
<a:bind value="person.firstName; save-when:self.onChange"/> <textbox id="firstName"/>
Or specify directly on the Component's attribute:
<textbox id="firstName" value="@{person.firstName, save-when='self.onChange'}"/>
However, you don't generally specify the save-when tag. If you don't specify it, the default events are used depends on the natural charactieric of the component's attribute as defined in lang-addon.xml. For example, the save-when of Label.value is default to none while that of Textbox.value is default to self.onChange. That is, the following example is the same as the above one.
Declare in front of the Component:
<a:bind value="person.firstName"/> <textbox id="firstName"/>
Or specifies directly on the Component's attribute:
<textbox id="firstName" value="@{person.firstName}"/>
On the other hand, you might not specify the save-when tag nor you want the default events to be used. Then you can specify a "none" keyword or simply leave empty to indicate such cases.
<a:bind value="person.firstName; save-when:none;"/> <textbox id="firstName"/>or
<a:bind value="person.firstName; save-when: ;"/> <textbox id="firstName"/>or
<textbox id="firstName" value="@{person.firstName, save-when='none'}"/>
or
<textbox id="firstName" value="@{person.firstName, save-when=''}"/>
Since 3.0.0, DataBinder supports validation phase before saving attribute content into bean property when triggered by the specified event in save-when tag. It will fire onBindingSave event to the data-binding component and then fire onBindingValidate to the triggering component before really saving component attribute contents into bean's property. So application developers get the chance to handle the value validatiion before saving. In the following example when end user click the "savebtn" button, an "onBindingSave" is first fired to "firtName" and "lastName" textboxes and then an "onBindingValidate" is fired to "savebtn" button. Application developers can register proper event handlers to do what they want to do.
<textbox id="firstName" value="@{person.firstName, save-when="savebtn.onClick"}" onBindingSave="..."/>
<textbox id="lastName" value="@{person.lastName, save-when="savebtn.onClick"}" onBindingSave="..."/>
<button id="savebtn" label="save" onBindingValidate="..."/>
Note that the original textbox constraint mechanism is still there. This DataBinder validation phase is an add-on feature that can be applied to all components and attributes that use data binding mechanism.
DataBinder.loadAll() and DataBinder.loadComponent(org.zkoss.zk.ui.Component) would load only those attributes
with "both" or "load" access mode. The DataBinder.saveAll() and
DataBinder.saveComponent(org.zkoss.zk.ui.Component) would save only those attributes with "both" or "save" access mode. If you
don't specify it, the default access mode depends on the natural characteristic of the component's attribute
as defined in lang-addon.xml. For example, Label.value is default to "load" access mode while Textbox.value
is default to "both" access mode. For example, the following code snips tells DataBinder that Textbox "firstName"
would allowing doing save into bean only not the other way.
Declare in front of the Component:
<a:bind value="person.firstName;access:save;"/> <textbox id="firstName"/>
Or specify directly on the Component's attribute:
<textbox id="firstName" value="@{person.firstName, access='save'}"/>
TypeConverter interface.
It is used to convert the value between component attribute and bean field. Multiple definition is NOT allowed
and the later defined would override the previous defined one.
Most of the time you don't have to specify this since this DataBinder supports converting most commonly
used types. However, if you specify the TypeConverter class name, this DataBinder will new an instance and use
it to cast the class.
AnnotateDataBinderInit,
DataBinder| Field Summary |
|---|
| Fields inherited from class org.zkoss.zkplus.databind.DataBinder |
|---|
_collectionItemMap, NULLIFY, TEMPLATE, TEMPLATEMAP, VARNAME |
| Constructor Summary | |
|---|---|
AnnotateDataBinder(org.zkoss.zk.ui.Component comp)
Constructor that read all binding annotations in the components inside the specified component (inclusive). |
|
AnnotateDataBinder(org.zkoss.zk.ui.Component[] comps)
Constructor that read all binding annotations of the given components array. |
|
AnnotateDataBinder(org.zkoss.zk.ui.Component[] comps,
boolean defaultConfig)
Constructor that read all binding annotations of the given component array. |
|
AnnotateDataBinder(org.zkoss.zk.ui.Component comp,
boolean defaultConfig)
Constructor that read all binding annotations in the components inside the specified component (inclusive). |
|
AnnotateDataBinder(org.zkoss.zk.ui.Desktop desktop)
Constructor that read all binding annotations of the components inside the specified desktop. |
|
AnnotateDataBinder(org.zkoss.zk.ui.Desktop desktop,
boolean defaultConfig)
Constructor that read all binding annotations of the components inside the specified desktop. |
|
AnnotateDataBinder(org.zkoss.zk.ui.Page page)
Constructor that read all binding annotations of the components inside the specified page. |
|
AnnotateDataBinder(org.zkoss.zk.ui.Page page,
boolean defaultConfig)
Constructor that read all binding annotations of the components inside the specified page. |
|
| Method Summary |
|---|
| Methods inherited from class org.zkoss.zkplus.databind.DataBinder |
|---|
addBinding, addBinding, addBinding, addBinding, addBinding, addCollectionItem, bindBean, existBinding, existsBindings, getBinding, getBindingCollectionItem, getBindings, init, isDefaultConfig, loadAll, loadAttribute, loadComponent, loadPropertyAnnotation, removeBinding, saveAll, saveAttribute, saveComponent, setDefaultConfig, setupTemplateComponent |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Constructor Detail |
|---|
public AnnotateDataBinder(org.zkoss.zk.ui.Desktop desktop)
desktop - the ZUML desktop.public AnnotateDataBinder(org.zkoss.zk.ui.Page page)
page - the ZUML page.public AnnotateDataBinder(org.zkoss.zk.ui.Component comp)
comp - the ZUML component.public AnnotateDataBinder(org.zkoss.zk.ui.Component[] comps)
comps - the Component array.
public AnnotateDataBinder(org.zkoss.zk.ui.Desktop desktop,
boolean defaultConfig)
desktop - the ZUML desktop.defaultConfig - whether load default binding configuration defined in lang-addon.xml
public AnnotateDataBinder(org.zkoss.zk.ui.Page page,
boolean defaultConfig)
page - the ZUML page.defaultConfig - whether load default binding configuration defined in lang-addon.xml
public AnnotateDataBinder(org.zkoss.zk.ui.Component[] comps,
boolean defaultConfig)
comps - the Component arraydefaultConfig - whether load default binding configuration defined in lang-addon.xml
public AnnotateDataBinder(org.zkoss.zk.ui.Component comp,
boolean defaultConfig)
comp - the ZUML component.defaultConfig - whether load default binding configuration defined in lang-addon.xml
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||