Practices Of Using Spring In ZK"
m (→Introduction) |
m (correct highlight (via JWB)) |
||
(23 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
− | |||
− | |||
{{Template:Smalltalk_Author| | {{Template:Smalltalk_Author| | ||
|author=Ian YT Tsai, Engineer, Potix Corporation | |author=Ian YT Tsai, Engineer, Potix Corporation | ||
− | |date=October | + | |date=October 23, 2012 |
|version=ZK 6 | |version=ZK 6 | ||
}} | }} | ||
Line 12: | Line 10: | ||
First, I'll list the prerequisites of the demo application. Then I'll focus on the detail configuration of this application stack and guide you through how to use [http://www.zkoss.org/javadoc/latest/zk/org/zkoss/zkplus/spring/DelegatingVariableResolver.html ZK Spring DelegatingVariableResolver] in your ZK code with some programming tips of the Spring part design. | First, I'll list the prerequisites of the demo application. Then I'll focus on the detail configuration of this application stack and guide you through how to use [http://www.zkoss.org/javadoc/latest/zk/org/zkoss/zkplus/spring/DelegatingVariableResolver.html ZK Spring DelegatingVariableResolver] in your ZK code with some programming tips of the Spring part design. | ||
− | If you have already read [http://books.zkoss.org/wiki/Small_Talks/2012/September/Practices_Of_Using_CDI_In_ZK Practices Of Using CDI In ZK], this article is the counterpart of it in Spring. | + | If you have already read '''"Practices Of Using CDI In ZK"'''<ref> [http://books.zkoss.org/wiki/Small_Talks/2012/September/Practices_Of_Using_CDI_In_ZK Practices Of Using CDI In ZK] </ref>, this article is the counterpart of it in Spring. |
=Develop Environment Preparation= | =Develop Environment Preparation= | ||
− | + | You can get source code from github <ref> Visit [https://github.com/hawkchen/smalltalk/downloads github smalltalk] and click "Download as zip" button or use a git client to clone the whole repository. </ref>. If your are familiar with Git, you can also clone my repository. | |
− | If your are familiar with Git, you can also clone my | + | |
===IDE Setup=== | ===IDE Setup=== | ||
In this article, we use Eclipse with M2Eclipse to manage our Maven Project. | In this article, we use Eclipse with M2Eclipse to manage our Maven Project. | ||
− | |||
# '''M2Eclipse''': a Maven management Eclipse plugin. | # '''M2Eclipse''': a Maven management Eclipse plugin. | ||
# '''RunJettyRun''': a simple Jetty Server which is very easy to use with M2Eclipse. | # '''RunJettyRun''': a simple Jetty Server which is very easy to use with M2Eclipse. | ||
===Demo Project Setup=== | ===Demo Project Setup=== | ||
− | If you are a Maven user and already cloned my repository , | + | If you are a Maven user and have already cloned my repository, this project is a Maven project, you can use Eclipse '''Import Existing Project''' function to import it. |
− | If you get the code by downloading | + | If you get the code by downloading the zip file, unpack it, and put them to your preferred project type. |
+ | |||
+ | = The Demo Application= | ||
+ | The demo application of this article is the same one in [[ZK Essentials/Laying out Your ZK Components/Using ZK Borderlayout| ZK Essentials]]; it is an online order management system. | ||
− | + | [[File:zk_cdi_integration_demo.png | 500px | center | Demo: Order Management System]] | |
− | |||
− | This | + | This application consists of 4 parts: |
<ol> | <ol> | ||
− | <li>'''Login''', when | + | <li>'''Login''', when the user requests the URL: http://localhost:8080/springZkDemo for the first time, the request will be redirected to the login page and ask user to perform the login process.</li> |
− | <li>''' | + | <li>'''Product view''', after logging-in, user will be redirected back to main page which has three fragments, the first one is product view which displays all available products.</li> |
− | <li>''' | + | <li>'''Shopping cart view''', At the east part of main view which displays user's shopping cart content, user can add, remove and change quantity of products in cart.</li> |
− | <li>''' | + | <li>'''Order view''', The bottom of the main page displays user's order and order details of each order.</li> |
</ol> | </ol> | ||
− | ===Entity Beans | + | ===Entity Beans === |
− | In this demo application we have several entity beans | + | In this demo application we have several entity beans under package '''org.zkoss.springdemo.bean''' |
<ul> | <ul> | ||
− | <li>Product, a product with several | + | <li><code>Product</code>, a product with several properties like name, price, quantity</li> |
− | <li>CartItem, a shopping cart item which | + | <li><code>CartItem</code>, a shopping cart item which references to a <code>Product</code>.</li> |
− | <li>Order, an order | + | <li><code>Order</code>, When a users submit all items in a shopping cart, we create an order. |
− | < | + | <li><code>OrderItem</code>, an item that comes from submitted <code>CartItem</code></li> |
− | <li>User, a user | + | <li><code>User</code>, a user who logins into the application.</li> |
</ul> | </ul> | ||
=Using Spring in ZK Application= | =Using Spring in ZK Application= | ||
− | Just like a normal Spring web application, you have to configure some listener, context parameter and filter in ''WEB-INF/web.xml'' to make Spring | + | Just like a normal Spring web application, you have to configure some listener, context parameter and filter in ''WEB-INF/web.xml'' to make Spring manage its application context properly for different levels of scope. |
− | The configuration | + | |
+ | The configuration looks like this: | ||
+ | '''web.xml''' | ||
<source lang="xml"> | <source lang="xml"> | ||
<!-- Declares where the Spring application context setting is --> | <!-- Declares where the Spring application context setting is --> | ||
<context-param> | <context-param> | ||
<param-name>contextConfigLocation</param-name> | <param-name>contextConfigLocation</param-name> | ||
− | <param-value> | + | <param-value>WEB-INF/applicationContext.xml</param-value> |
</context-param> | </context-param> | ||
Line 67: | Line 68: | ||
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> | <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> | ||
</listener> | </listener> | ||
+ | </source> | ||
+ | |||
+ | Our demo project uses the classpath scanning feature to register beans. It detects classes in specified packages with stereotype annotations (e.g. <code>@Component</code>) and registers them as Spring managed beans. | ||
+ | |||
+ | '''applicationContext.xml''' | ||
+ | <source lang="xml"> | ||
+ | <!-- AutowiredAnnotationBeanPostProcessor and CommonAnnotationBeanPostProcessor are both | ||
+ | included implicitly--> | ||
+ | <context:component-scan base-package="org.zkoss.springdemo" /> | ||
+ | <!-- JPA and transaction manager configuration --> | ||
+ | ... | ||
</source> | </source> | ||
=Persistence Layer= | =Persistence Layer= | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | <!-- | |
+ | In this Demo we use JPA as our persistence layer solution. There are 3 options for JPA setup in a Spring environment: | ||
+ | # LocalEntityManagerFactoryBean. This is suitable for simple deployment environments where the application uses only JPA for data access. | ||
+ | # Obtaining an EntityManagerFactory from JNDI. Use this option when deploying to a Java EE 5 server. | ||
+ | # LocalContainerEntityManagerFactoryBean. This option gives full control over EntityManagerFactory configuration and is appropriate for environments where fine-grained customization is required. | ||
+ | |||
+ | We choose the third one here to keep this demo project simple but still close to real case. | ||
+ | |||
+ | == JPA Configuration in Spring == | ||
+ | As the <context-param> declaration in ''WEB-INF/web.xml'', we put our Spring application context configuration file in ''WEB-INF/applicationContext.xml'' | ||
+ | |||
+ | Opening our applicationContext.xml, the JPA related configuration part is briefed below: | ||
<source language="xml"> | <source language="xml"> | ||
− | < | + | <bean id="emf" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"/> |
− | |||
− | |||
− | |||
− | |||
<bean id="txManager" class="org.springframework.orm.jpa.JpaTransactionManager"> | <bean id="txManager" class="org.springframework.orm.jpa.JpaTransactionManager"> | ||
<property name="entityManagerFactory" ref="emf" /> | <property name="entityManagerFactory" ref="emf" /> | ||
</bean> | </bean> | ||
− | |||
<tx:annotation-driven transaction-manager="txManager" /> | <tx:annotation-driven transaction-manager="txManager" /> | ||
</source> | </source> | ||
− | |||
− | |||
− | |||
− | '''bean | + | * LIne 1: To get and use a JPA Entity Manager, we need to register an Entity Manager Factory. In Spring, ''org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean'' is the bean that can simply construct a factory in application. |
+ | * Line 3: Declare a transaction manager for JPA. | ||
+ | * Line 7: enable the configuration of transactional behavior based on annotations. | ||
+ | --> | ||
+ | In our spring configuration, we have declared class path scanning element which implicitly registers <code> PersistenceAnnotationBeanPostProcessor</code> for us and a transaction manager. Spring can understand <code>@PersistenceContext</code> both at field and method level and inject proper <code>EntityManager</code> in current transaction. | ||
+ | |||
+ | === Implement DAO on JPA === | ||
+ | |||
+ | In our project, we implement DAO (Data Access Object) pattern for the persistence layer with injected EntityManger and this DAO doesn't depends on any Spring's classes. | ||
+ | |||
+ | <source lang="java" highlight="4"> | ||
− | |||
− | |||
− | |||
@Repository | @Repository | ||
− | public class | + | public class ProductDAO { |
+ | |||
@PersistenceContext | @PersistenceContext | ||
− | EntityManager em; | + | private EntityManager em; |
− | + | ||
− | + | public List<Product> findAll() { | |
− | public | + | Query query = em.createQuery("from products"); |
− | + | List<Product> products = query.getResultList(); | |
− | + | return products; | |
− | |||
} | } | ||
... | ... | ||
} | } | ||
</source> | </source> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | =Service Layer= | |
− | + | Service Layer is composed of business objects which are put in package <code>org.zkoss.springdemo.service</code>. | |
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
==Business Object Design practice== | ==Business Object Design practice== | ||
In this demo application, we have several main business objects which provides a set of logical API to interact with view. | In this demo application, we have several main business objects which provides a set of logical API to interact with view. | ||
They are: | They are: | ||
<ul> | <ul> | ||
− | <li>org.zkoss.springdemo. | + | <li>org.zkoss.springdemo.service.ProductManager</li> |
− | <li>org.zkoss.springdemo. | + | <li>org.zkoss.springdemo.service.UserOrderManager</li> |
− | <li>org.zkoss.springdemo. | + | <li>org.zkoss.springdemo.service.UserCredentialManager</li> |
− | <li>org.zkoss.springdemo. | + | <li>org.zkoss.springdemo.service.ShoppingCartManager</li> |
</ul> | </ul> | ||
Let's use them to see how to design your business object in some common scenario. | Let's use them to see how to design your business object in some common scenario. | ||
− | === | + | |
− | + | ||
+ | ===Singleton Scope Practice=== | ||
+ | If a business object is stateless, we can declare it as a singleton bean. For example, '''org.zkoss.springdemo.service.ProductManager''', it only provides a list of available products and do not save any user's or product's state. Therefore, we should declare it as a singleton bean. | ||
+ | |||
<source lang="java"> | <source lang="java"> | ||
+ | @Service | ||
public class ProductManager { | public class ProductManager { | ||
+ | @Autowired | ||
private ProductDAO productDao; | private ProductDAO productDao; | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
public List<Product> findAllAvailable() { | public List<Product> findAllAvailable() { | ||
return productDao.findAllAvailable(); | return productDao.findAllAvailable(); | ||
Line 164: | Line 163: | ||
} | } | ||
</source> | </source> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | === | + | |
− | + | ===Session Scope Practice=== | |
+ | A business object which needs to keep state across multiple requests for individual user should be "session" scope. For example, <code>ShoppingCartManager </code> contains selected products of a user. | ||
+ | |||
<source lang="java"> | <source lang="java"> | ||
− | @ | + | @Component("shoppingCart") |
− | @Scope( | + | @Scope("session") |
− | public class | + | public class ShoppingCartManager implements ShoppingCart { |
− | |||
− | |||
− | |||
− | + | ... | |
− | + | } | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</source> | </source> | ||
− | + | The <code>UserCredentialManager </code> keeps the user credential. So we should make them "session" scope to keep data. | |
− | |||
− | |||
− | |||
− | |||
− | |||
<source lang="java"> | <source lang="java"> | ||
+ | @Component | ||
+ | @Scope("session") | ||
public class UserCredentialManager implements Serializable{ | public class UserCredentialManager implements Serializable{ | ||
− | + | ||
− | |||
private User user; | private User user; | ||
− | + | ... | |
− | + | } | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</source> | </source> | ||
=Presentation Layer= | =Presentation Layer= | ||
− | This layer is about how to use BO in ZK's view, the java classes that controlling zk views are all under '''org.zkoss.springdemo. | + | This layer is about how to use BO in ZK's view, the java classes that controlling zk views are all under '''org.zkoss.springdemo.controller'''. |
In this application we demonstrate how to use Spring bean in ZK MVC controller: | In this application we demonstrate how to use Spring bean in ZK MVC controller: | ||
− | * ''org.zkoss.springdemo. | + | * ''org.zkoss.springdemo.controller.LoginViewCtrl'' |
− | * ''org.zkoss.springdemo. | + | * ''org.zkoss.springdemo.controller.ProductViewCtrl'' |
and how to use Spring bean in ZK MVVM view model bean: | and how to use Spring bean in ZK MVVM view model bean: | ||
− | * ''org.zkoss.springdemo. | + | * ''org.zkoss.springdemo.controller.OrderViewViewModel'' |
− | * ''org.zkoss.springdemo. | + | * ''org.zkoss.springdemo.controller.ShoppingCartViewModel'' |
==Context Injection in ZK== | ==Context Injection in ZK== | ||
Adopting Spring's context to ZK view context is very simple, you simply use ZK's '''org.zkoss.zkplus.spring.DelegatingVariableResolver'''. | Adopting Spring's context to ZK view context is very simple, you simply use ZK's '''org.zkoss.zkplus.spring.DelegatingVariableResolver'''. | ||
− | Here we will discuss | + | Here we will discuss several circumstances in which you can use ZK's Spring ''DelegatingVariableResolver''. |
+ | |||
===ZK's Listener=== | ===ZK's Listener=== | ||
− | In the login process | + | In the login process, we have a ''WorkbenchInit'' declared in index.zul. It's one of [http://books.zkoss.org/wiki/ZK_Configuration_Reference/zk.xml/The_listener_Element ZK's listeners] that allow you to intercept ZK's life cycle. This listener calls <code>UserCredentialManager.isAuthenticated()</code> to verify user's authentication. |
+ | |||
+ | [[File:zk_cdi_integration_login_proc.png]] | ||
+ | |||
+ | So we need to get Spring managed bean in ZK's listener first. To get Spring managed bean from them, the easiest way is to use <code>SpringUtil.getBean("userCredentialManager")</code>. | ||
− | + | <source lang="java" highlight="6"> | |
− | <source lang="java"> | ||
public class WorkbenchInit implements Initiator { | public class WorkbenchInit implements Initiator { | ||
private UserCredentialManager userCredentialManager; | private UserCredentialManager userCredentialManager; | ||
Line 248: | Line 218: | ||
public void doInit(Page page, @SuppressWarnings("rawtypes") Map arg) throws Exception { | public void doInit(Page page, @SuppressWarnings("rawtypes") Map arg) throws Exception { | ||
if(userCredentialManager==null){ | if(userCredentialManager==null){ | ||
− | userCredentialManager = (UserCredentialManager) | + | userCredentialManager = (UserCredentialManager)SpringUtil.getBean("userCredentialManager"); |
− | |||
} | } | ||
if (!userCredentialManager.isAuthenticated()) { | if (!userCredentialManager.isAuthenticated()) { | ||
Line 257: | Line 226: | ||
//... | //... | ||
</source> | </source> | ||
− | |||
− | In Listener scenario we use a programmatic approach to get managed bean. In ZK MVC controller, we can use annotations for variable wiring to save coding effort. For example, in ''org.zkoss.spring demo. | + | |
− | <source lang="java"> | + | In Listener scenario we use a programmatic approach to get managed bean. In ZK MVC controller, we can use annotations for variable wiring to save coding effort. For example, in ''org.zkoss.spring demo.controller.LoginViewCtrl'': |
+ | <source lang="java" highlight="1,9"> | ||
@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class) | @VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class) | ||
public class LoginViewCtrl extends SelectorComposer<Window> { | public class LoginViewCtrl extends SelectorComposer<Window> { | ||
Line 283: | Line 252: | ||
//... | //... | ||
</source> | </source> | ||
− | We use '''@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class)''' to annotate ''LoginViewCtrl'' which tells super class ''SelectorComposer'' that this controller will based on Spring context to do variable wiring. | + | * Line 1: We use '''<code>@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class)</code>''' to annotate ''<code>LoginViewCtrl</code>'' which tells super class ''SelectorComposer'' that this controller will based on Spring context to do variable wiring. |
− | + | * Line 9: We can use '''<code>@WireVariable</code>''' to wire UserCredentialManager like Spring's <code>@Autowired</code>. As you can see, by default if the field's name is the name of that Spring bean, the instance will be wired automatically. | |
===ZK MVVM=== | ===ZK MVVM=== | ||
− | In ZK MVVM, the way to do variable wiring is very similar to ZK MVC, let's use ''org.zkoss.springdemo. | + | In ZK MVVM, the way to do variable wiring is very similar to ZK MVC, let's use ''org.zkoss.springdemo.controller.OrderViewViewModel'' for example: |
− | <source lang="java"> | + | <source lang="java" highlight="1,4"> |
@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class) | @VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class) | ||
public class OrderViewViewModel { | public class OrderViewViewModel { | ||
Line 328: | Line 297: | ||
} | } | ||
</source> | </source> | ||
− | We reuse '''@VariableResolver''' and '''@WireVariable''' annotations here, which makes our View Model object becomes very clean to both ZK view and data. | + | * Line 1,4: We reuse '''@VariableResolver''' and '''@WireVariable''' annotations here, which makes our View Model object becomes very clean to both ZK view and data. |
=Conclusion= | =Conclusion= | ||
− | In this series of articles(with the other two: [http://books.zkoss.org/wiki/Small_Talks/2012/September/Practices_Of_Using_CDI_In_ZK Practices Of Using CDI In ZK], [http://books.zkoss.org/wiki/Small_Talks/2012/Aug/Starting_A_Web_Application_Based_On_ZK_CDI_JPA_and_Jetty Starting A Web Application Based On ZK CDI JPA and Jetty] ) I showed how to start a web application stack based on two of most famous application frameworks(CDI, Spring) with ZK | + | In this series of articles(with the other two: [http://books.zkoss.org/wiki/Small_Talks/2012/September/Practices_Of_Using_CDI_In_ZK Practices Of Using CDI In ZK], [http://books.zkoss.org/wiki/Small_Talks/2012/Aug/Starting_A_Web_Application_Based_On_ZK_CDI_JPA_and_Jetty Starting A Web Application Based On ZK CDI JPA and Jetty] ) I showed how to start a web application stack based on two of the most famous application frameworks(CDI, Spring) with ZK. As you can see, the usage of these framework's context are totally the same in ZK. |
+ | |||
+ | = References = | ||
+ | <references/> | ||
{{Template:CommentedSmalltalk_Footer| | {{Template:CommentedSmalltalk_Footer| | ||
|name=Potix Corporation | |name=Potix Corporation | ||
}} | }} |
Latest revision as of 04:20, 20 January 2022
Ian YT Tsai, Engineer, Potix Corporation
October 23, 2012
ZK 6
Introduction
Spring Framework is one of the most common frameworks for Java web developers. In this article, I'll introduce how to integrate ZK, Spring and Hibernate together to build a web application. First, I'll list the prerequisites of the demo application. Then I'll focus on the detail configuration of this application stack and guide you through how to use ZK Spring DelegatingVariableResolver in your ZK code with some programming tips of the Spring part design.
If you have already read "Practices Of Using CDI In ZK"[1], this article is the counterpart of it in Spring.
Develop Environment Preparation
You can get source code from github [2]. If your are familiar with Git, you can also clone my repository.
IDE Setup
In this article, we use Eclipse with M2Eclipse to manage our Maven Project.
- M2Eclipse: a Maven management Eclipse plugin.
- RunJettyRun: a simple Jetty Server which is very easy to use with M2Eclipse.
Demo Project Setup
If you are a Maven user and have already cloned my repository, this project is a Maven project, you can use Eclipse Import Existing Project function to import it. If you get the code by downloading the zip file, unpack it, and put them to your preferred project type.
The Demo Application
The demo application of this article is the same one in ZK Essentials; it is an online order management system.
This application consists of 4 parts:
- Login, when the user requests the URL: http://localhost:8080/springZkDemo for the first time, the request will be redirected to the login page and ask user to perform the login process.
- Product view, after logging-in, user will be redirected back to main page which has three fragments, the first one is product view which displays all available products.
- Shopping cart view, At the east part of main view which displays user's shopping cart content, user can add, remove and change quantity of products in cart.
- Order view, The bottom of the main page displays user's order and order details of each order.
Entity Beans
In this demo application we have several entity beans under package org.zkoss.springdemo.bean
Product
, a product with several properties like name, price, quantityCartItem
, a shopping cart item which references to aProduct
.Order
, When a users submit all items in a shopping cart, we create an order.OrderItem
, an item that comes from submittedCartItem
User
, a user who logins into the application.
Using Spring in ZK Application
Just like a normal Spring web application, you have to configure some listener, context parameter and filter in WEB-INF/web.xml to make Spring manage its application context properly for different levels of scope.
The configuration looks like this: web.xml
<!-- Declares where the Spring application context setting is -->
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>WEB-INF/applicationContext.xml</param-value>
</context-param>
<!-- Spring Context Initialization & Request scope Handling -->
<listener>
<listener-class>org.springframework.web.context.request.RequestContextListener</listener-class>
</listener>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
Our demo project uses the classpath scanning feature to register beans. It detects classes in specified packages with stereotype annotations (e.g. @Component
) and registers them as Spring managed beans.
applicationContext.xml
<!-- AutowiredAnnotationBeanPostProcessor and CommonAnnotationBeanPostProcessor are both
included implicitly-->
<context:component-scan base-package="org.zkoss.springdemo" />
<!-- JPA and transaction manager configuration -->
...
Persistence Layer
In our spring configuration, we have declared class path scanning element which implicitly registers PersistenceAnnotationBeanPostProcessor
for us and a transaction manager. Spring can understand @PersistenceContext
both at field and method level and inject proper EntityManager
in current transaction.
Implement DAO on JPA
In our project, we implement DAO (Data Access Object) pattern for the persistence layer with injected EntityManger and this DAO doesn't depends on any Spring's classes.
@Repository
public class ProductDAO {
@PersistenceContext
private EntityManager em;
public List<Product> findAll() {
Query query = em.createQuery("from products");
List<Product> products = query.getResultList();
return products;
}
...
}
Service Layer
Service Layer is composed of business objects which are put in package org.zkoss.springdemo.service
.
Business Object Design practice
In this demo application, we have several main business objects which provides a set of logical API to interact with view. They are:
- org.zkoss.springdemo.service.ProductManager
- org.zkoss.springdemo.service.UserOrderManager
- org.zkoss.springdemo.service.UserCredentialManager
- org.zkoss.springdemo.service.ShoppingCartManager
Let's use them to see how to design your business object in some common scenario.
Singleton Scope Practice
If a business object is stateless, we can declare it as a singleton bean. For example, org.zkoss.springdemo.service.ProductManager, it only provides a list of available products and do not save any user's or product's state. Therefore, we should declare it as a singleton bean.
@Service
public class ProductManager {
@Autowired
private ProductDAO productDao;
public List<Product> findAllAvailable() {
return productDao.findAllAvailable();
}
}
Session Scope Practice
A business object which needs to keep state across multiple requests for individual user should be "session" scope. For example, ShoppingCartManager
contains selected products of a user.
@Component("shoppingCart")
@Scope("session")
public class ShoppingCartManager implements ShoppingCart {
...
}
The UserCredentialManager
keeps the user credential. So we should make them "session" scope to keep data.
@Component
@Scope("session")
public class UserCredentialManager implements Serializable{
private User user;
...
}
Presentation Layer
This layer is about how to use BO in ZK's view, the java classes that controlling zk views are all under org.zkoss.springdemo.controller. In this application we demonstrate how to use Spring bean in ZK MVC controller:
- org.zkoss.springdemo.controller.LoginViewCtrl
- org.zkoss.springdemo.controller.ProductViewCtrl
and how to use Spring bean in ZK MVVM view model bean:
- org.zkoss.springdemo.controller.OrderViewViewModel
- org.zkoss.springdemo.controller.ShoppingCartViewModel
Context Injection in ZK
Adopting Spring's context to ZK view context is very simple, you simply use ZK's org.zkoss.zkplus.spring.DelegatingVariableResolver. Here we will discuss several circumstances in which you can use ZK's Spring DelegatingVariableResolver.
ZK's Listener
In the login process, we have a WorkbenchInit declared in index.zul. It's one of ZK's listeners that allow you to intercept ZK's life cycle. This listener calls UserCredentialManager.isAuthenticated()
to verify user's authentication.
So we need to get Spring managed bean in ZK's listener first. To get Spring managed bean from them, the easiest way is to use SpringUtil.getBean("userCredentialManager")
.
public class WorkbenchInit implements Initiator {
private UserCredentialManager userCredentialManager;
public void doInit(Page page, @SuppressWarnings("rawtypes") Map arg) throws Exception {
if(userCredentialManager==null){
userCredentialManager = (UserCredentialManager)SpringUtil.getBean("userCredentialManager");
}
if (!userCredentialManager.isAuthenticated()) {
Executions.getCurrent().sendRedirect("login.zul");
}
}
//...
In Listener scenario we use a programmatic approach to get managed bean. In ZK MVC controller, we can use annotations for variable wiring to save coding effort. For example, in org.zkoss.spring demo.controller.LoginViewCtrl:
@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class)
public class LoginViewCtrl extends SelectorComposer<Window> {
@Wire
private Textbox nameTxb, passwordTxb;
@Wire
private Label mesgLbl;
@WireVariable
private UserCredentialManager userCredentialManager;
@Listen("onClick=#confirmBtn; onOK=#passwordTxb")
public void doLogin() {
userCredentialManager.login(nameTxb.getValue(), passwordTxb.getValue());
if (userCredentialManager.isAuthenticated()) {
Executions.getCurrent().sendRedirect("index.zul");
} else {
mesgLbl.setValue("Your User Name or Password is invalid!");
}
}
//...
- Line 1: We use
@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class)
to annotateLoginViewCtrl
which tells super class SelectorComposer that this controller will based on Spring context to do variable wiring. - Line 9: We can use
@WireVariable
to wire UserCredentialManager like Spring's@Autowired
. As you can see, by default if the field's name is the name of that Spring bean, the instance will be wired automatically.
ZK MVVM
In ZK MVVM, the way to do variable wiring is very similar to ZK MVC, let's use org.zkoss.springdemo.controller.OrderViewViewModel for example:
@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class)
public class OrderViewViewModel {
@WireVariable
private UserOrderManager userOrderManager;
private Order selectedItem;
public Order getSelectedItem() {
return selectedItem;
}
@NotifyChange("selectedItem")
public void setSelectedItem(Order selectedItem) {
this.selectedItem = selectedItem;
}
public List<Order> getOrders() {
return userOrderManager.findAll();
}
@Command
@NotifyChange({"orders", "selectedItem"})
public void cancelOrder() {
if (getSelectedItem() == null) {
return;
}
userOrderManager.cancelOrder(getSelectedItem());
setSelectedItem(null);
}
@GlobalCommand
@NotifyChange("orders")
public void submitNewOrder(
@BindingParam("cartItems")List<CartItem> cartItems
,@BindingParam("orderNote") String orderNote){
userOrderManager.createOrder( cartItems, orderNote);
}
}
- Line 1,4: We reuse @VariableResolver and @WireVariable annotations here, which makes our View Model object becomes very clean to both ZK view and data.
Conclusion
In this series of articles(with the other two: Practices Of Using CDI In ZK, Starting A Web Application Based On ZK CDI JPA and Jetty ) I showed how to start a web application stack based on two of the most famous application frameworks(CDI, Spring) with ZK. As you can see, the usage of these framework's context are totally the same in ZK.
References
- ↑ Practices Of Using CDI In ZK
- ↑ Visit github smalltalk and click "Download as zip" button or use a git client to clone the whole repository.
Comments
Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License. |