Author
Ian YT Tsai, Engineer, Potix Corporation

Date
October 23, 2012

Version
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, quantity
CartItem, a shopping cart item which references to a Product.
Order, When a users submit all items in a shopping cart, we create an order.
OrderItem, an item that comes from submitted CartItem
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;
	}
...
}

Logic Layer

Logic Layer is a layer for business objects of this demo. In this demo application, all objects about this layer has been put in package org.zkoss.springdemo.web.model.

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.web.model.ProductManager
org.zkoss.springdemo.web.model.UserOrderManager
org.zkoss.springdemo.web.model.UserCredentialManager
org.zkoss.springdemo.web.model.ShoppingCart

Let's use them to see how to design your business object in some common scenario.

Application Scope Practice

In org.zkoss.springdemo.web.model.ProductManager, as the scenario here is to provide a list of available products for view to display, the code is very simple:

public class ProductManager {
	
	private ProductDAO productDao;

	public ProductDAO getProductDao() {
		return productDao;
	}
	public void setProductDao(ProductDAO productDao) {
		this.productDao = productDao;
	}
	public List<Product> findAllAvailable() {
		return productDao.findAllAvailable();
	}
}

As you can see, this bean has nothing but a productDao attribute, the scope declaration and bean id are all defined in app-context.xml:

<bean id="productManager" scope="application"
	class="org.zkoss.springdemo.web.model.ProductManager">
	<property name="productDao" ref="productDAO" />
</bean>

Inconsistent Scope handling

Though our ProductManager is application scoped, the ProductDAO which Spring injected has a request scoped life-cycle, this causes a scope inconsistent problem that needs to be solved. To deal with this inconsistency, Spring has a Scoped Proxy mechanism which is based on Spring AOP and we need to define the proxy mode in ProductDAO class annotation declaration:

@Repository
@Scope(value="request", proxyMode=ScopedProxyMode.TARGET_CLASS)
public class ProductDAO{
	...

At the back-end with this declaration, Spring will use CGLIB to create a proxy class to pretend our ProductDao and inject it into our ProductManager to make sure every time when user calls: productDao.findAllAvailable(), the manager would still work fine.

Session Scope Practice

In web logical layer design, a business object which needs to keep state across multiple requests should be stored in session. In this Spring demo app, business layered beans' meta info are all declared in app-context.xml:

	<bean id="shoppingCart" scope="session"
		class="org.zkoss.springdemo.web.model.ShoppingCartSessionImpl">
		<property name="userCredentialManager" ref="userCredentialManager" />
	</bean>

To identify if a managed bean should be session scoped or not, you can check if it contains unmanaged state-related member fields in bean class. For example in our demo application while user tries to request http://localhost:8080/springZkDemo/index.zul we need to check if current user is authenticated, if not, we'll redirect him to login.zul for the login process:

In order to do this, in this demo, org.zkoss.springdemo.web.model.UserCredentialManager which is a session designed to scoped object maintaining the state of user credential:

public class UserCredentialManager implements Serializable{
	public UserCredentialManager(){}
	
	private User user;

	private UserDAO userDao;
	public UserDAO getUserDao() {
		return userDao;
	}
	public void setUserDao(UserDAO userDao) {
		this.userDao = userDao;
	}
	public synchronized void login(String name, String password) {
//....

As you can see above, the UserCredentialManager has a login(name, password) method and has a User bean stored inside and in the app-context.xml:

	<bean id="userCredentialManager" scope="session"
		class="org.zkoss.springdemo.web.model.UserCredentialManager">
		<aop:scoped-proxy/>
		<property name="UserDao" ref="userDAO" />
	</bean>

Presentation Layer

This layer is about how to use BO in ZK's view, java classes that controls zk views are all under org.zkoss.springdemo.web.ui.ctrl. In this application we demonstrate how to use Spring bean in ZK MVC controller:

org.zkoss.springdemo.web.ui.ctrl.LoginViewCtrl
org.zkoss.springdemo.web.ui.ctrl.ProductViewCtrl

and how to use Spring bean in ZK MVVM view model bean:

org.zkoss.springdemo.web.ui.ctrl.OrderViewViewModel
org.zkoss.springdemo.web.ui.ctrl.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 3 circumstances in which you can use ZK's Spring DelegatingVariableResolver.

ZK's Listener

In the login process example above, we have a WorkbenchInit declared in index.zul, let's see how to get managed bean in ZK's listener (ex: org.zkoss.zk.ui.util.Initiator).

In ZK, we have a bunch of Listeners that you can do some interception or flow control with. To get Spring managed bean from them, the easiest way is to construct a new DelegatingVariableResolver instance:

public class WorkbenchInit implements Initiator {	
	private UserCredentialManager userCredentialManager;

	public void doInit(Page page, @SuppressWarnings("rawtypes") Map arg) throws Exception {
		if(userCredentialManager==null){
			userCredentialManager = (UserCredentialManager) 
			new DelegatingVariableResolver().resolveVariable("userCredentialManager");
		}
		if (!userCredentialManager.isAuthenticated()) {
			Executions.getCurrent().sendRedirect("login.zul");
		}
	}
//...

As illustrated above, we can get our session object userCredentialManager by calling resolveVariable(String) through DelegatingVariableResolver in an Initiator.

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.web.ui.ctrl.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!");
		}
	}
//...

We use @VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class) to annotate LoginViewCtrl which tells super class SelectorComposer that this controller will be based on Spring context to do variable wiring. Then in the member field declaration part, we can use @WireVariable to wire UserCredentialManager. 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.web.ui.ctrl.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);
	}
}

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.

Comments

↑ 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.

[1] Practices Of Using CDI In ZK

[2] Visit github smalltalk and click "Download as zip" button or use a git client to clone the whole repository.

[1]

[2]

Anonymous

Practices Of Using Spring In ZK

Namespaces

More

Page actions

Contents