The Theory of Using ZK with Databases"
Tmillsclare (talk | contribs) (Created page with '{{ZKEssentialsPageHeader}} ZK is predominantly a server centric framework thus developers are not required to leverage any special mechanism to transfer data from the server to …') |
Tmillsclare (talk | contribs) m |
||
| Line 1: | Line 1: | ||
{{ZKEssentialsPageHeader}} | {{ZKEssentialsPageHeader}} | ||
| − | ZK is predominantly a server centric framework thus developers are not required to leverage any special mechanism to transfer data from the server to the client | + | ZK is predominantly a server centric framework thus developers are not required to leverage any special mechanism to transfer data from the server to the client. |
| − | Fundamentally, as discussed in previous sections, data is provided to the view using a model | + | Fundamentally, as discussed in previous sections, data is provided to the view using a model which is a collection type, usually a <mp>List</mp>. For detailed information please [[ZK_Essentials/Displaying_Information_Using_Grid/Using_a_ListModel_and_RowRenderer | click here]]. |
The sequence of displaying the data in the view is shown below. | The sequence of displaying the data in the view is shown below. | ||
| Line 10: | Line 10: | ||
| − | With ZK handling the transfer of data to the client the process is substantially easier | + | With ZK handling the transfer of data to the client the process is substantially easier. A ZK developer is able to leverage any application or ORM framework such as Spring and Hibernate respectively without needing to perform any special task. |
| − | If you are familiar with Hibernate you do not need to read any further as the | + | If you are familiar with Hibernate you do not need to read any further as a the standard List of objects retrieved from ORM frameworks is compatible with ZK's model concept. Thus using the knowledge we gained in previous sections you can construct your application. |
| − | + | This chapter introduces those unfamiliar with ORM framworks to Hibernate and ZK. The following sections provide a simple tutorial on refactoring our current application to make use of persistent storage. | |
{{ZKEssentialsPageFooter}} | {{ZKEssentialsPageFooter}} | ||
Revision as of 10:45, 9 November 2010
This article is out of date, please refer to http://books.zkoss.org/zkessentials-book/master/ for more up to date information.
ZK is predominantly a server centric framework thus developers are not required to leverage any special mechanism to transfer data from the server to the client.
Fundamentally, as discussed in previous sections, data is provided to the view using a model which is a collection type, usually a List. For detailed information please click here.
The sequence of displaying the data in the view is shown below.
With ZK handling the transfer of data to the client the process is substantially easier. A ZK developer is able to leverage any application or ORM framework such as Spring and Hibernate respectively without needing to perform any special task.
If you are familiar with Hibernate you do not need to read any further as a the standard List of objects retrieved from ORM frameworks is compatible with ZK's model concept. Thus using the knowledge we gained in previous sections you can construct your application.
This chapter introduces those unfamiliar with ORM framworks to Hibernate and ZK. The following sections provide a simple tutorial on refactoring our current application to make use of persistent storage.