BT

Spring 3.1 RC1: Environments, Comprehensive @Configuration, Cache, c: namespace, Java 7

by Bienvenido David on Oct 29, 2011 |

SpringSource has released the first release candidate of Spring 3.1. Spring 3.1.0.RC1 contains the following new features:

  • Environment Abstraction and Bean Profiles
  • Comprehensive @Configuration
  • Cache Abstraction
  • c: namespace
  • Enhanced MVC Support
  • Enhanced JPA Support
  • Hibernate 4.0 and Quartz 2.0 Support
  • Servlet 3.0 Support
  • Java 7 with JDBC 4.1 and ForkJoinPool

The Spring 3.1 feature set is now complete and the Spring 3.1 GA release is planned for late November 2011. Here's a quick run down of the new features of Spring 3.1.

 

Environment Abstraction and Bean Profiles

Spring 3.1 introduces the concept of environment profiles. A common use case is the setting up of beans that are different between development, QA and production environments. A typical example is going against a standalone DataSource in development versus looking up the DataSource from JNDI in production. Another example is a beans profile for profiling that can easily be turned on or off. You can add a profile attribute on a beans element in XML or add @Profile annotation in code. Note that a Spring bean can be assigned to multiple profiles.

	<beans profile="dev">
		...
	</beans>
	@Profile("dev")
	public class Bean {
		...
	}

These profiles can be activated through the spring.profiles.active property which may be specified through an environment variable, a JVM system property, a Servlet <init-param> in web.xml or JNDI. These profiles can also be activated through code using Environment.setActiveProfiles(String ...). To make bean profiles work, nested beans elements are now allowed in the Spring XML, although constrained only at the end of the file. Note that it's recommended to keep your bean topology as close as possible between environments, so your application gets properly tested across environments.

 

You also use the Environment.containsProperty() method to search for properties across the different property sources. This property resolution also works for ${placeholder} variables in XML bean definitions.

Comprehensive @Configuration

Java-based application configuration has been enhanced and now has equivalent annotations to XML namespace functionality. @Enable annotations on @Configuration classes have been developed to match the functionality of XML namespace elements like <context:component-scan/>, <tx:annotation-driven/> and <mvc:annotation-driven>. Here's a list of the new annotations.

	org.springframework.context.annotation.Configuration
	org.springframework.context.annotation.ComponentScan
	org.springframework.context.annotation.EnableLoadTimeWeaving
	org.springframework.context.annotation.EnableAspectJAutoProxy
	org.springframework.scheduling.annotation.EnableScheduling
	org.springframework.scheduling.annotation.EnableAsync
	org.springframework.transaction.annotation.EnableTransactionManagement
	org.springframework.web.servlet.config.annotation.EnableWebMvc

The TestContext framework has been overhauled with first-class support for @Configuration classes and environment profiles. The @ContextConfiguration annotation now supports using @Configuration classes for configuring the Spring TestContext. The @ActiveProfiles annotation has also been added to support declarative configuration of profiles.

	@RunWith(SpringJUnit4ClassRunner.class)
	@ContextConfiguration(loader = AnnotationConfigContextLoader.class)
	@ActiveProfiles("dev")
	public class Test {

		@Configuration
		static class ContextConfiguration {
			...
		}

		...
	}

 

Cache Abstraction

Spring 3.1 provides support for transparently adding caching through the new @Cacheable annotation, or the <cache:advice> element if you prefer XML.

	<beans
		...
		xmlns:cache="http://www.springframework.org/schema/cache"
		http://www.springframework.org/schema/cache
		http://www.springframework.org/schema/cache/spring-cache.xsd">

		<cache:annotation-driven />

		...
	</beans>

	@Cacheable("cache")
	public String get(String s) {
		...

@Cacheable applies caching to Java methods, checking each time the annotated method is invoked. If the method has already been called with the given arguments, the cached result is returned and the actual method is not executed. Of course, this only works for methods that are guaranteed to return the same result for a given set of arguments. Two caching implementations available out of the box are for JDK java.util.concurrent.ConcurrentMap and Ehcache. There is also the @CacheEvict annotation, which allows methods to trigger a cache eviction, used to remove stale or unused data in the cache. Other features of the new Caching abstraction include custom cache key generation and conditional caching.

 

c: namespace

Similar to the p: namespace, Spring 3.1 has introduced the new c: namespace which allows attributes for configuring constructor arguments rather then nested <constructor-arg> elements.

	  <-- constructor-arg -->
	  <bean ...>
		  <constructor-arg value="val" />
	  </bean>

	  <-- c: namespace -->
	  <bean ... c:arg="val">

 

Enhanced MVC Support

Spring 3.1 has revised MVC processing with flash attribute support, the new @RequestPart annotation, and REST support refinements with respect to URI templates, path variable handling and content type specification.

Flash attributes provide a way for one request to store attributes intended for use in another, most commonly used when using redirects like the Post/Redirect/Get pattern. Flash attributes are saved and made available to the request after the redirect and then removed immediately. Concurrency issues are possible with this approach, so flash attributes are associated with the path and query parameters of the target redirect URL to minimize this problem. A @RequestMapping method can accept an argument of type RedirectAttributes and use it to add flash attributes.

	@RequestMapping(value = "/", method = RequestMethod.POST)
	public String foo(RedirectAttributes redirectAttributes) {
		...
	}

 

The new @RequestPart annotation can be used to associate a "multipart/form-data" request part with a method argument. It allows you to have the content of a specific multipart passed through an HttpMessageConverter, taking into consideration the multipart content-type.

	@RequestMapping(value="/", method = RequestMethod.POST)
	public String foo(@RequestPart("file") MultipartFile file) {
		...
	}

Spring 3.1 also introduces a new set of classes for processing requests with annotated controllers, namely RequestMappingHandlerMapping, RequestMappingHandlerAdapter and ExceptionHandlerExceptionResolver. These classes are replacements for DefaultAnnotationHandlerMapping, AnnotationMethodHandlerAdapter and AnnotationMethodHandlerExceptionResolver respectively. These new classes were developed to make annotation controller support classes more customizable and extensible. The use of these new classes is recommended going forward.

 

You can now narrow the request mapping by specifying a list of consumable or producible media types. For consumable media types, the request will be matched only if the Content-Type request header matches the specified type. For producible media types, the request will be matched only if the Accept request header matches the specified type.

	@RequestMapping(value = "/", method = RequestMethod.POST, consumes="application/json")
	public void foo() {
		...
	}

	@RequestMapping(value = "/", method = RequestMethod.POST, produces="application/json")
	public void bar() {
		...
	}

There are also URI template variable enhancements. URI template variables are now used in addition to request parameters when binding a request to @ModelAttribute arguments. @PathVariable method argument values are also merged into the model before rendering. A redirect string can contain placeholders for URI variables, and a @ModelAttribute method argument can be instantiated from a URI template variable as long as there is a registered Converter or PropertyEditor.

 

Enhanced JPA Support

With Spring 3.1, the JPA EntityManagerFactory can be bootstrapped without persistence.xml or other metadata files. Using the LocalContainerEntityManagerFactoryBean packagesToScan property, you can specify the base packages to scan for @Entity classes. This is similar to AnnotationSessionFactoryBean's property of the same name for native Hibernate setup, and to Spring's component-scan feature for regular Spring beans.

Hibernate 4.0 and Quartz 2.x Support

Spring 3.1 now supports Hibernate 4.0, as well Quartz 2.x, while still preserving compatibility with older versions. For more information on Hibernate 4 support, see the Javadoc for classes within the new org.springframework.orm.hibernate4 package. The package is intentionally minimal, relying on native Hibernate builder APIs for building a SessionFactory. Quartz 2.x has converted some classes to interfaces and thus older versions of Spring are not compatible and will throw a java.lang.InstantiationError. Spring 3.1 has addressed this issue while still maintaining compatibility with Quartz 1.x.

Servlet 3.0 Support

Spring 3.1 now supports the Servlet 3.0 ServletContainerInitializer and MultipartResolver. Spring's new WebApplicationInitializer is built on top of ServletContainerInitializer to provide a programmatic alternative to web.xml. The following is an example of replacing web.xml with a WebApplicationInitializer. The link is a commit page from SpringSource's greenhouse repository.

https://github.com/SpringSource/greenhouse/commit/213d2c742d472e602defcde801dd118e098d73c6

 

Java 7 with JDBC 4.1 and ForkJoinPool

Initially planned for Spring 3.2, Java 7 is now supported in Spring 3.1, with JDBC 4.1 getting auto-detected and with basic support for ForkJoinPool. Spring's DataSource and RowSet adapters have been updated for compatibility with JDBC 4.1. ForkJoinPoolFactoryBean has been introduced, which is a Spring FactoryBean that builds and exposes a preconfigured ForkJoinPool.

Additional Features

Spring 3.1 now supports injection against non-standard JavaBeans setters, useful with method-chaining, where setter methods return a reference to 'this'. In earlier Spring versions, for Spring to inject against a property method, the method had to conform strictly to JavaBeans property rules, namely that the setter method must return void.

Note that conversation support has been dropped from the 3.1 feature set, due to the lack of demand, but is still under consideration for Spring 3.2. Conversation support has been called "HttpSession++", a session mechanism with a more flexible lifecycle and storage options, and the ability to be associated with a browser tab.

To try out these new features, you can download the Spring 3.1 RC1 release from the Spring Community Downloads page. If you use Maven, you can get Spring 3.1.0.RC1 from the http://maven.springframework.org/milestone Repository.

	<repository>
		<id>org.springframework.maven.milestone</id>
		<name>Spring Maven Milestone Repository</name>
		<url>http://maven.springframework.org/milestone</url>
	</repository>

	<dependency>
		<groupId>org.springframework</groupId>
		<artifactId>spring-core</artifactId>
		<version>3.1.0.RC1</version>
	</dependency>

For more information, visit the Spring 3.1 RC1 Reference Documentation, Javadoc API and Changelog. You can also ask questions in the Spring community forum.

 

Hello stranger!

You need to Register an InfoQ account or to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Great summary! by Mark Serrano

Great summary of the latest additions to Spring 3.1

I've personally used the profile, cache, enhanced media types, and JPA support. Simple but effective. If you're a Spring 3.x user, it would be odd not to use them. They aren't necessary but makes developing Spring apps way easier.

Web Profile by Javier Zamora

When Does Spring Support Java EE Web Profile 6?
never, or only a few features

HttpSession++ by Luis Trigueiros

Hi,
I'm passion about spring framework, but recently I having read a bit about Seam I found the programming model very attractive, I don't think we can get the same thing with webflow, the seamless integration of workflow engine in the application, can we ?
Thank you Oscar

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

3 Discuss

Educational Content

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2013 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT