From Documentation

Jump to: navigation, search








Contents

Overview

Spring Framework is a popular application development framework for enterprise Java. One key element is its infrastructural support: a light-weighted container that manages POJOs as Spring beans and maintain beans' dependency injection relationship. We will talk about several integration ways including wiring and accessing beans in various conditions. We assume that readers have knowledge in Spring's basic configuration and concept such as bean scope, we will therefore not cover these topics here. Please refer to Spring documentation. We write these source code examples based on Spring 3.0.5.RELEASE.


Configuration

The minimal Maven dependency you need is :

    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-web</artifactId>
      <version>3.0.5.RELEASE</version>
    </dependency>

If you use scoped-proxy with CGLIB-based class proxy, you will need cglib.

    <dependency>
      <groupId>cglib</groupId>
      <artifactId>cglib</artifactId>
      <version>2.2.2</version>
    </dependency>

Icon info.png Note: If you don't use Maven, please refer to Spring Framework Reference Documentation to know which JAR file you need.


To integrate ZK application and Spring , the minimal configuration you have to setup is following:

Spring related configuration in web.xml

...
	<!-- Loads the Spring application context configuration -->
	<listener>
		<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
	</listener>
	<!-- For using web scoped bean -->
	<listener>
		<listener-class>org.springframework.web.context.request.RequestContextListener</listener-class>
	</listener>
...


You can enable Spring's classpath scanning to register beans.

WEB-INF/applicationContext.xml


<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:context="http://www.springframework.org/schema/context"
       xsi:schemaLocation="
           http://www.springframework.org/schema/beans
           http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
           http://www.springframework.org/schema/context
           http://www.springframework.org/schema/context/spring-context-3.0.xsd">

	<!-- Scans for application @Components to deploy -->
	<context:component-scan base-package="org.zkoss.reference.developer" />

</beans>
  • Line 12: Apply @Component on those classes that you plan to register them as Spring beans and specify base package of those classes.

Access a Spring Bean in a ZUL

ZUL provides a feature called variable resolver that allows users to access Spring bean using EL expressions. This is how you do it; simply put the below directive on top of a ZUML page:

<?variable-resolver class="org.zkoss.zkplus.spring.DelegatingVariableResolver" ?>

Then, in the rest of your page, you can access a Spring-Managed bean directly using its bean id.

Assume that we have two beans:


@Component
@Scope("session")
public class UserPreference {
...
}
  • User preference should be distinct for each user but shared among multiple requests. It is suitable to be a session scoped bean.


@Component
public class SystemConfiguration {
...
}
  • As system configuration should be shared within the whole application, this should be a singleton bean.


Access Spring beans with EL

<?variable-resolver class="org.zkoss.zkplus.spring.DelegatingVariableResolver"?>
<window title="Access Bean with different scopes" border="normal" width="700px"
	apply="org.zkoss.reference.developer.composer.ResolverComposer">
	<vlayout>
		<hlayout>
			User Preference :
			<label id="sessionValue">${userPreference.value}</label>
		</hlayout>
		<hlayout>
			System Configuration :
			<label id="singletonValue">${systemConfiguration.value}</label>
		</hlayout>
	</vlayout>
</window>
  • The delegating variable-resolver will look-up the bean named userPreference automatically for you.

Wire a Spring Bean

Using Scoped-Proxy

We recommend you to apply scoped-proxy on every bean that is used in a composer( or a ViewModel). There are at least two reasons. First, in "Spring Framework Reference" mentions that when you inject a shorter-lived scoped bean into a longer-lived scoped bean, you should use scoped-proxy bean. The proxy can fetch the real shorter-lived scoped bean for longer-lived scoped bean and delegate all method calls onto the real bean. Because the scope of composer ( or a ViewModel) doesn't match any of Spring's bean scopes, using scoped-proxy ensures you call a method on the right bean. Second, a reference to a bean might be invalid after session replication in clustering environment. Hence, even you use a singleton bean, it's better to use the scoped-proxy.

To apply scoped-proxy to a bean, just apply @Scope with proxyMode specified on a bean.

@Service("orderService")
@Scope(proxyMode=ScopedProxyMode.TARGET_CLASS)
public class OrderServiceImpl implements OrderService {
...
}
  • Line 2: If you use ScopedProxyMode.TARGET_CLASS, you need CGLIB library in the classpath of your application.

Wire a Spring bean in a Composer

It is a very common requirement that we need to use a Spring bean in a composer, for example calling a service layer object to perform business logic. If a composer is a Spring-managed bean, we can just use Spring's injection mechanism like auto-wire to wire dependencies. However, we don't recommend this approach (explain in the previous section).

Therefore, ZK provides another way to wire a Spring bean to a composer which is not a Spring-managed bean. When we apply a composer to a ZUL with org.zkoss.zkplus.spring.DelegatingVariableResolver mentioned in the previous section, we can apply annotation, @WireVariable on a variable we want to wire a Spring bean with. ZK will then wire the corresponding Spring bean with the variable using variable name that's same as the bean's name. Alternatively, you can specify the bean's name with @WireVariable("beanName").

Example code is as follow:


A composer that wires Spring beans


public class ResolverComposer extends SelectorComposer<Window> {

	@WireVariable
	private OrderService orderService;
	
	@Wire("#number")
	private Label label;
	
	@Override
	public void doAfterCompose(Window comp) throws Exception {
		super.doAfterCompose(comp);
		label.setValue(Integer.toString(orderService.list().size()));
	}

}

A ZUL with Spring variable resolver


<?variable-resolver class="org.zkoss.zkplus.spring.DelegatingVariableResolver"?>
<window title="Access Bean with different scopes" border="normal" width="700px"
	apply="org.zkoss.reference.developer.spring.composer.ResolverComposer">
...
</window>

Wire a Spring bean in a ViewModel

Wiring a Spring bean in a ViewModel is very similar to the case in a composer, simply apply @WireVariable with variable resolver. In the example below we put variable resolver in a zul with a directive.

A ViewModel that wires a Spring bean


public class OrderVM {

	@WireVariable
	OrderService orderService;

	public List<Order> getOrders() {
		if (orders == null) {
			//init the list
			orders = orderService.list();
		}
		return orders;
	}
	...
}

The zul uses OrderVM with a Spring variable resolver


<?variable-resolver class="org.zkoss.zkplus.spring.DelegatingVariableResolver"?>
<zk>
<window title="Order Management" border="normal" width="600px" apply="org.zkoss.bind.BindComposer" 
viewModel="@id('vm') @init('org.zkoss.reference.developer.spring.order.viewmodel.OrderVM')" 
validationMessages="@id('vmsgs')">

...
</window>
</zk>

Adding Variable Resolver to a Composer (or ViewModel)

Adding a variable resolver to a ZUL will make it available to all composers on the ZUL. If you want to add a variable resolver to a specific composer (or ViewModel) only, you should apply the annotation

@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class)

on the class that inherits SelectorComposer or a ViewModel. Then, apply @WireVariable on variables like we did in the previous section.

Example code are as follows:

@VariableResolver(org.zkoss.zkplus.spring.DelegatingVariableResolver.class)
public class SpringComposer extends SelectorComposer<Window> {

	@WireVariable
	private OrderService orderService;
...
}

Retrieve a Spring Bean Programmatically

org.zkoss.zkplus.spring.SpringUtil is a utility class which allows you to get Spring-managed beans in Java.

public class SpringComposer extends SelectorComposer<Window> {

	@Wire("#number")
	private Label label;
	
	@Override
	public void doAfterCompose(Window comp) throws Exception {
		super.doAfterCompose(comp);
		OrderService orderService = (OrderService)SpringUtil.getBean("orderService");
		label.setValue(Integer.toString(orderService.list().size()));
	}
}


Warning: Register a Composer (or ViewModel) as a Spring bean

Many developers tend to register ZK's composer (or ViewModel) as a Spring-managed bean, but we do not recommend this approach because none of Spring's scopes matches correctly with the life cycle of the composers, please see ZK Developer's Reference/MVC/Controller/Wire Variables for more details. The scope of a composer is "desktop" scope that is shorter than "session" and longer than "prototype". Only ZK knows when to create composers (or ViewModel), so it's better to let composers be managed by ZK.

If you insist on making Spring manage the composers (or ViewModel), "prototype" scope is a feasible scope. However, you need to use with care; each time you try to resolve a composer bean, you will get a new instance of a composer. If the composer stores some states, it will cause inconsistency of states among multiple composers.

Integrate Spring Webflow and Security

ZK also provides integration to other Spring projects such as Spring Security and Spring Webflow with ZK Spring. Please refer to ZK Spring Essentials for details.

Example Source Code

All source code of examples used in this chapter can be found in here.



Version History

Last Update : 2013/8/8


Version Date Content
6.5.0 November 2012 Rewrite for improvement.



Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.



You got stuck here?
Let us know how we can improve this page
For specific questions please use the forum