Activates Data Binding Manager"
From Documentation
Line 14: | Line 14: | ||
<window apply="org.zkoss.demo.MyComposer"> | <window apply="org.zkoss.demo.MyComposer"> | ||
</window> | </window> | ||
− | </zk | + | </zk> |
</source> | </source> | ||
Line 23: | Line 23: | ||
<window apply="org.zkoss.demo.MyComposer,org.zkoss.zkplus.databind.AnnotateDataBindingComposer"> | <window apply="org.zkoss.demo.MyComposer,org.zkoss.zkplus.databind.AnnotateDataBindingComposer"> | ||
</window> | </window> | ||
− | </zk | + | </zk> |
</source> | </source> | ||
Revision as of 07:33, 1 September 2011
The Data Binding Manager can be activated by defining the page Initializer at the top of every page.
<?init class="org.zkoss.zkplus.databind.AnnotateDataBinderInit" ?>
For example, the page may looks like
<?init class="org.zkoss.zkplus.databind.AnnotateDataBinderInit"?>
<zk>
<window apply="org.zkoss.demo.MyComposer">
</window>
</zk>
After ZK 5.0.8 there is a new and cleverer way in which users can adopt to do achieve the same outcome – by defining a dedicated Composer – AnnotateDataBindingComposer. The page with this way may looks like
<zk>
<window apply="org.zkoss.demo.MyComposer,org.zkoss.zkplus.databind.AnnotateDataBindingComposer">
</window>
</zk>
For more information, please refer to the relative blog post Databinding Composer
This initiator class does the following things:
- Creates an AnnotateDataBinder instance.
- Sets the AnnotateDataBinder instance as a variable with the name "binder" stored in the component as specified in arg0 "component-path".(if arg0 is not specified, use Page instead.)
- Calls DataBinder.loadAll() to initiate all UI components from the associated data source.
Version History
Version | Date | Content |
---|---|---|