root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity

[SPR-8240] Updating the "new in 3.1" chapter regarding new testing support; polishing the TestContext Framework section of the reference manual.

This commit is contained in:
Sam Brannen 2011-10-09 23:32:01 +00:00
parent 71396ac07b
commit 6248135a4f
2 changed files with 308 additions and 144 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

433
spring-framework-reference/src/new-in-3.1.xml
View File

@ -5,22 +5,24 @@
<title>New Features and Enhancements in Spring 3.1</title>
<para>Building on the support introduced in Spring 3.0, Spring 3.1 is
currently under development, and at the time of this writing Spring 3.1 M2
has just been released.</para>
currently under development, and at the time of this writing Spring 3.1 RC1
is being prepared for release.</para>
<section id="new-in-3.1-features-overview">
<title>Overview of new features</title>
<para>This is a list of new features for Spring 3.1. Most features
do not yet have dedicated reference documentation but do have
Javadoc. In these cases, fully-qualified classnames are given.</para>
<para>This is a list of new features for Spring 3.1. Most features do not
yet have dedicated reference documentation but do have Javadoc. In such
cases, fully-qualified class names are given.</para>
<section>
<title>Cache Abstraction</title>
<itemizedlist>
<listitem>
<para><xref linkend="cache"/></para>
<para><xref linkend="cache" /></para>
</listitem>
<listitem>
<para><ulink
url="http://blog.springsource.com/2011/02/23/spring-3-1-m1-caching/">
@ -28,102 +30,135 @@
</listitem>
</itemizedlist>
</section>
<section>
<title>Bean Definition Profiles</title>
<itemizedlist>
<listitem>
<para><ulink
url="http://blog.springsource.com/2011/02/11/spring-framework-3-1-m1-released/">
XML profiles</ulink> (SpringSource Team Blog)</para>
</listitem>
<listitem>
<para><ulink
url="http://blog.springsource.com/2011/02/14/spring-3-1-m1-introducing-profile/">
Introducing @Profile</ulink> (SpringSource Team Blog)</para>
</listitem>
<listitem>
<para>See org.springframework.context.annotation.Configuration Javadoc</para>
<para>See org.springframework.context.annotation.Configuration
Javadoc</para>
</listitem>
<listitem>
<para>See org.springframework.context.annotation.Profile Javadoc</para>
<para>See org.springframework.context.annotation.Profile
Javadoc</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Environment Abstraction</title>
<itemizedlist>
<listitem>
<para><ulink
url="http://blog.springsource.com/2011/02/11/spring-framework-3-1-m1-released/">
Environment Abstraction</ulink> (SpringSource Team Blog)</para>
</listitem>
<listitem>
<para>See org.springframework.core.env.Environment Javadoc</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>PropertySource Abstraction</title>
<itemizedlist>
<listitem>
<para><ulink
url="http://blog.springsource.com/2011/02/15/spring-3-1-m1-unified-property-management/">
Unified Property Management</ulink> (SpringSource Team Blog)</para>
</listitem>
<listitem>
<para>See org.springframework.core.env.Environment Javadoc</para>
</listitem>
<listitem>
<para>See org.springframework.core.env.PropertySource Javadoc</para>
</listitem>
<listitem>
<para>See org.springframework.context.annotation.PropertySource Javadoc</para>
<para>See org.springframework.context.annotation.PropertySource
Javadoc</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Code equivalents for Spring's XML namespaces</title>
<para>Code-based equivalents to popular Spring XML namespace elements such as
&lt;tx:annotation-driven/&gt; and &lt;mvc:annotation-driven&gt; have been
developed, in the form of <interfacename>@Enable</interfacename> annotations,
for use in conjunction with Spring's <interfacename>@Configuration</interfacename>
<para>Code-based equivalents to popular Spring XML namespace elements
such as &lt;tx:annotation-driven/&gt; and &lt;mvc:annotation-driven&gt;
have been developed, in the form of
<interfacename>@Enable</interfacename> annotations, for use in
conjunction with Spring's <interfacename>@Configuration</interfacename>
classes.</para>
<itemizedlist>
<listitem>
<para>See org.springframework.scheduling.annotation.Configuration Javadoc</para>
<para>See org.springframework.scheduling.annotation.Configuration
Javadoc</para>
</listitem>
<listitem>
<para>See org.springframework.scheduling.annotation.EnableAsync Javadoc</para>
<para>See org.springframework.scheduling.annotation.EnableAsync
Javadoc</para>
</listitem>
<listitem>
<para>See org.springframework.scheduling.annotation.EnableScheduling
Javadoc</para>
</listitem>
<listitem>
<para>See
org.springframework.scheduling.annotation.EnableTransactionManagement
Javadoc</para>
</listitem>
<listitem>
<para>See
org.springframework.scheduling.annotation.EnableLoadTimeWeaving
Javadoc</para>
</listitem>
<listitem>
<para>See org.springframework.scheduling.annotation.EnableWebMvc Javadoc</para>
<para>See org.springframework.scheduling.annotation.EnableWebMvc
Javadoc</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Builder-style APIs for code-based Hibernate configuration</title>
<para><classname>SessionFactoryBuilder</classname> and
<classname>AnnotationSessionFactoryBuilder</classname> classes have been designed
for use within <interfacename>@Bean</interfacename> methods in
<classname>AnnotationSessionFactoryBuilder</classname> classes have been
designed for use within <interfacename>@Bean</interfacename> methods in
<interfacename>@Configuration</interfacename> classes.</para>
<itemizedlist>
<listitem>
<para>See org.springframework.orm.hibernate3.SessionFactoryBuilder Javadoc</para>
<para>See org.springframework.orm.hibernate3.SessionFactoryBuilder
Javadoc</para>
</listitem>
<listitem>
<para>See
org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBuilder
@ -131,55 +166,114 @@
</listitem>
</itemizedlist>
</section>
<section>
<title>TestContext framework support for @Configuration classes and bean definition profiles</title>
<para>The <interfacename>@ContextConfiguration</interfacename> annotation now
supports supplying <interfacename>@Configuration</interfacename> classes for
configuring the Spring <classname>TestContext</classname>. In addition, a new
<interfacename>@ActiveProfiles</interfacename> annotation has been introduced
to support declarative configuration of active bean definition profiles in
<interfacename>ApplicationContext</interfacename> integration tests.</para>
<title>TestContext framework support for @Configuration classes and bean
definition profiles</title>
<para>The <interfacename>@ContextConfiguration</interfacename>
annotation now supports supplying
<interfacename>@Configuration</interfacename> classes for configuring
the Spring <classname>TestContext</classname>. In addition, a new
<interfacename>@ActiveProfiles</interfacename> annotation has been
introduced to support declarative configuration of active bean
definition profiles in <interfacename>ApplicationContext</interfacename>
integration tests.</para>
<itemizedlist>
<listitem>
<para>See org.springframework.test.context.ContextConfiguration Javadoc</para>
<para><ulink
url="http://blog.springsource.com/2011/06/21/spring-3-1-m2-testing-with-configuration-classes-and-profiles/">Spring
3.1 M2: Testing with @Configuration Classes and Profiles</ulink>
(SpringSource Team Blog)</para>
</listitem>
<listitem>
<para>See <xref linkend="testcontext-framework" /></para>
</listitem>
<listitem>
<para>See <xref linkend="testcontext-ctx-management-javaconfig" />
and
<interfacename>org.springframework.test.context.ContextConfiguration</interfacename>
Javadoc</para>
</listitem>
<listitem>
<para>See
<interfacename>org.springframework.test.context.ActiveProfiles</interfacename>
Javadoc</para>
</listitem>
<listitem>
<para>See
<interfacename>org.springframework.test.context.SmartContextLoader</interfacename>
Javadoc</para>
</listitem>
<listitem>
<para>See
<interfacename>org.springframework.test.context.support.DelegatingSmartContextLoader</interfacename>
Javadoc</para>
</listitem>
<listitem>
<para>See
<interfacename>org.springframework.test.context.support.AnnotationConfigContextLoader</interfacename>
Javadoc</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>c: namespace for more concise constructor injection</title>
<itemizedlist>
<listitem>
<para><xref linkend="beans-c-namespace"/></para>
<para><xref linkend="beans-c-namespace" /></para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Support for injection against non-standard JavaBeans setters</title>
<para>Prior to Spring 3.1, in order to inject against a property method it had to
conform strictly to JavaBeans property signature rules, namely that any 'setter'
method must be void-returning. It is now possible in Spring XML to specify
setter methods that return any object type. This is useful when considering
designing APIs for method-chaining, where setter methods return a reference to
'this'.</para>
<title>Support for injection against non-standard JavaBeans
setters</title>
<para>Prior to Spring 3.1, in order to inject against a property method
it had to conform strictly to JavaBeans property signature rules, namely
that any 'setter' method must be void-returning. It is now possible in
Spring XML to specify setter methods that return any object type. This
is useful when considering designing APIs for method-chaining, where
setter methods return a reference to 'this'.</para>
</section>
<section>
<title>Support for Servlet 3 code-based configuration of Servlet Container</title>
<para>The new <interfacename>WebApplicationInitializer</interfacename> builds atop
Servlet 3.0's <interfacename>ServletContainerInitializer</interfacename> support
to provide a programmatic alternative to the traditional web.xml.</para>
<title>Support for Servlet 3 code-based configuration of Servlet
Container</title>
<para>The new <interfacename>WebApplicationInitializer</interfacename>
builds atop Servlet 3.0's
<interfacename>ServletContainerInitializer</interfacename> support to
provide a programmatic alternative to the traditional web.xml.</para>
<itemizedlist>
<listitem>
<para>See org.springframework.web.WebApplicationInitializer Javadoc</para>
<para>See org.springframework.web.WebApplicationInitializer
Javadoc</para>
</listitem>
<listitem>
<para><ulink url="http://bit.ly/lrDHja">Diff from Spring's Greenhouse
reference application</ulink> demonstrating migration from web.xml to
<para><ulink url="http://bit.ly/lrDHja">Diff from Spring's
Greenhouse reference application</ulink> demonstrating migration
from web.xml to
<interfacename>WebApplicationInitializer</interfacename></para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Support for Servlet 3 MultipartResolver</title>
<itemizedlist>
<listitem>
<para>See
@ -188,120 +282,189 @@
</listitem>
</itemizedlist>
</section>
<section>
<title>JPA EntityManagerFactory bootstrapping without persistence.xml</title>
<para>In standard JPA, persistence units get defined through <literal>META-INF/persistence.xml</literal>
files in specific jar files which will in turn get searched for <literal>@Entity</literal> classes.
In many cases, persistence.xml does not contain more than a unit name and relies on defaults and/or
external setup for all other concerns (such as the DataSource to use, etc). For that reason, Spring 3.1
provides an alternative: <classname>LocalContainerEntityManagerFactoryBean</classname> accepts a
'packagesToScan' property, specifying base packages to scan for <literal>@Entity</literal> classes.
This is analogous to <classname>AnnotationSessionFactoryBean</classname>'s property of the same name
for native Hibernate setup, and also to Spring's component-scan feature for regular Spring beans.
Effectively, this allows for XML-free JPA setup at the mere expense of specifying a base package for
entity scanning: a particularly fine match for Spring applications which rely on component scanning
for Spring beans as well, possibly even bootstrapped using a code-based Servlet 3.0 initializer.</para>
<title>JPA EntityManagerFactory bootstrapping without
persistence.xml</title>
<para>In standard JPA, persistence units get defined through
<literal>META-INF/persistence.xml</literal> files in specific jar files
which will in turn get searched for <literal>@Entity</literal> classes.
In many cases, persistence.xml does not contain more than a unit name
and relies on defaults and/or external setup for all other concerns
(such as the DataSource to use, etc). For that reason, Spring 3.1
provides an alternative:
<classname>LocalContainerEntityManagerFactoryBean</classname> accepts a
'packagesToScan' property, specifying base packages to scan for
<literal>@Entity</literal> classes. This is analogous to
<classname>AnnotationSessionFactoryBean</classname>'s property of the
same name for native Hibernate setup, and also to Spring's
component-scan feature for regular Spring beans. Effectively, this
allows for XML-free JPA setup at the mere expense of specifying a base
package for entity scanning: a particularly fine match for Spring
applications which rely on component scanning for Spring beans as well,
possibly even bootstrapped using a code-based Servlet 3.0
initializer.</para>
</section>
<section>
<title>New HandlerMethod-based Support Classes For Annotated Controller Processing</title>
<para>Spring 3.1 introduces a new set of support classes for processing requests
with annotated controllers:</para>
<title>New HandlerMethod-based Support Classes For Annotated Controller
Processing</title>
<para>Spring 3.1 introduces a new set of support classes for processing
requests with annotated controllers:</para>
<itemizedlist>
<listitem>RequestMappingHandlerMapping</listitem>
<listitem>RequestMappingHandlerAdapter</listitem>
<listitem>ExceptionHandlerExceptionResolver</listitem>
<listitem>
<para><classname>RequestMappingHandlerMapping</classname></para>
</listitem>
<listitem>
<para><classname>RequestMappingHandlerAdapter</classname></para>
</listitem>
<listitem>
<para><classname>ExceptionHandlerExceptionResolver</classname></para>
</listitem>
</itemizedlist>
<para>These classes are a replacement for the existing:</para>
<itemizedlist>
<listitem>DefaultAnnotationHandlerMapping</listitem>
<listitem>AnnotationMethodHandlerAdapter</listitem>
<listitem>AnnotationMethodHandlerExceptionResolver</listitem>
<listitem>
<para><classname>DefaultAnnotationHandlerMapping</classname></para>
</listitem>
<listitem>
<para><classname>AnnotationMethodHandlerAdapter</classname></para>
</listitem>
<listitem>
<para><classname>AnnotationMethodHandlerExceptionResolver</classname></para>
</listitem>
</itemizedlist>
<para>The new classes were developed in response to many requests to make
annotation controller support classes more customizable and open for extension.
Whereas previously you could configure a custom annotated controller method
argument resolver, with the new support classes you can customize the
processing for any supported method argument or return value type.</para>
<para>The new classes were developed in response to many requests to
make annotation controller support classes more customizable and open
for extension. Whereas previously you could configure a custom annotated
controller method argument resolver, with the new support classes you
can customize the processing for any supported method argument or return
value type.</para>
<itemizedlist>
<listitem>See org.springframework.web.method.support.HandlerMethodArgumentResolver Javadoc</listitem>
<listitem>See org.springframework.web.method.support.HandlerMethodReturnValueHandler Javadoc</listitem>
</itemizedlist>
<listitem>
<para>See
org.springframework.web.method.support.HandlerMethodArgumentResolver
Javadoc</para>
</listitem>
<listitem>
<para>See
org.springframework.web.method.support.HandlerMethodReturnValueHandler
Javadoc</para>
</listitem>
</itemizedlist>
<para>A second notable difference is the introduction of a
<classname>HandlerMethod</classname> abstraction to represent an
<interface>@RequestMapping</interface> method. This abstraction is used
throughout by the new support classes as the <literal>handler</literal> instance.
For example a <classname>HandlerInterceptor</classname> can cast
the <literal>handler</literal> from <classname>Object</classname> to
<classname>HandlerMethod</classname> and get access to the target
throughout by the new support classes as the <literal>handler</literal>
instance. For example a <classname>HandlerInterceptor</classname> can
cast the <literal>handler</literal> from <classname>Object</classname>
to <classname>HandlerMethod</classname> and get access to the target
controller method, its annotations, etc.</para>
<para>The new classes are enabled by default by the MVC namespace and by
Java-based configuration via <interface>@EnableWebMvc</interface>. The
existing classes will continue to be available but use of the new classes is
recommended going forward.</para>
<para>The new classes are enabled by default by the MVC namespace and by
Java-based configuration via <interface>@EnableWebMvc</interface>. The
existing classes will continue to be available but use of the new
classes is recommended going forward.</para>
</section>
<section>
<title>"consumes" and "produces" conditions in <interface>@RequestMapping</interface></title>
<para>Improved support for specifying media types consumed by a method through the
<literal>'Content-Type'</literal> header as well as for producible types specified
through the <literal>'Accept'</literal> header.
See <xref linkend="mvc-ann-requestmapping-consumes"/> and
<xref linkend="mvc-ann-requestmapping-produces"/>
</para>
<title>"consumes" and "produces" conditions in
<interface>@RequestMapping</interface></title>
<para>Improved support for specifying media types consumed by a method
through the <literal>'Content-Type'</literal> header as well as for
producible types specified through the <literal>'Accept'</literal>
header. See <xref linkend="mvc-ann-requestmapping-consumes" /> and <xref
linkend="mvc-ann-requestmapping-produces" /></para>
</section>
<section>
<title>Flash Attributes and <interfacename>RedirectAttributes</interfacename></title>
<para>Flash attributes can now be stored in a <classname>FlashMap</classname>
and saved in the HTTP session to survive a redirect. For an overview of
the general support for flash attributes in Spring MVC
see <xref linkend="mvc-flash-attributes"/>.
</para>
<para>
In annotated controllers, an <interfacename>@RequestMapping</interfacename>
method can add flash attributes by declaring a method argument of type
<title>Flash Attributes and
<interfacename>RedirectAttributes</interfacename></title>
<para>Flash attributes can now be stored in a
<classname>FlashMap</classname> and saved in the HTTP session to survive
a redirect. For an overview of the general support for flash attributes
in Spring MVC see <xref linkend="mvc-flash-attributes" />.</para>
<para>In annotated controllers, an
<interfacename>@RequestMapping</interfacename> method can add flash
attributes by declaring a method argument of type
<interfacename>RedirectAttributes</interfacename>. This method argument
can now also be used to get precise control over the attributes used in
a redirect scenario. See <xref linkend="mvc-ann-redirect-attributes"/>
for more details.
</para>
a redirect scenario. See <xref linkend="mvc-ann-redirect-attributes" />
for more details.</para>
</section>
<section>
<title>URI Template Variable Enhancements</title>
<para>URI template variables from the current request are used in more places:
<itemizedlist>
<listitem>URI template variables are used in addition to request parameters
when binding a request to <interfacename>@ModelAttribute</interfacename>
method arguments.</listitem>
<listitem>@PathVariable method argument values are merged into the model
before rendering, except in views that generate content in an automated
fashion such as JSON serialization or XML marshalling.</listitem>
<listitem>A redirect string can contain placeholders for URI variables
(e.g. <literal>"redirect:/blog/{year}/{month}"</literal>). When expanding
the placeholders, URI template variables from the current request are
automatically considered.</listitem>
<listitem>An <interfacename>@ModelAttribute</interfacename> method argument
can be instantiated from a URI template variable provided there is a
registered Converter or PropertyEditor to convert from a String to the
target object type.</listitem>
</itemizedlist>
</para>
</section>
<section>
<title><interfacename>@Valid</interfacename> On
<interface>@RequestBody</interface> Controller Method Arguments</title>
<para>An <interface>@RequestBody</interface> method argument
can be annotated with <interface>@Valid</interface> to invoke automatic
validation similar to the support for
<interface>@ModelAttribute</interface> method arguments.
A resulting <classname>MethodArgumentNotValidException</classname> is
handled in the <classname>DefaultHandlerExceptionResolver</classname>
and results in a <literal>400</literal> response code.</para>
</section>
<section>
<title><interfacename>@RequestPart</interfacename> Annotation On Controller Method Arguments</title>
<para>This new annotation provides access to the content of a
"multipart/form-data" request part.
See <xref linkend="mvc-multipart-forms-non-browsers" /> and
<xref linkend="mvc-multipart"/>.</para>
<title>URI Template Variable Enhancements</title>
<para>URI template variables from the current request are used in more
places: <itemizedlist>
<listitem>
<para>URI template variables are used in addition to request
parameters when binding a request to
<interfacename>@ModelAttribute</interfacename> method
arguments.</para>
</listitem>
<listitem>
<para>@PathVariable method argument values are merged into the
model before rendering, except in views that generate content in
an automated fashion such as JSON serialization or XML
marshalling.</para>
</listitem>
<listitem>
<para>A redirect string can contain placeholders for URI variables
(e.g. <literal>"redirect:/blog/{year}/{month}"</literal>). When
expanding the placeholders, URI template variables from the
current request are automatically considered.</para>
</listitem>
<listitem>
<para>An <interfacename>@ModelAttribute</interfacename> method
argument can be instantiated from a URI template variable provided
there is a registered Converter or PropertyEditor to convert from
a String to the target object type.</para>
</listitem>
</itemizedlist></para>
</section>
<section>
<title><interfacename>@Valid</interfacename> On
<interface>@RequestBody</interface> Controller Method Arguments</title>
<para>An <interface>@RequestBody</interface> method argument can be
annotated with <interface>@Valid</interface> to invoke automatic
validation similar to the support for
<interface>@ModelAttribute</interface> method arguments. A resulting
<classname>MethodArgumentNotValidException</classname> is handled in the
<classname>DefaultHandlerExceptionResolver</classname> and results in a
<literal>400</literal> response code.</para>
</section>
<section>
<title><interfacename>@RequestPart</interfacename> Annotation On
Controller Method Arguments</title>
<para>This new annotation provides access to the content of a
"multipart/form-data" request part. See <xref
linkend="mvc-multipart-forms-non-browsers" /> and <xref
linkend="mvc-multipart" />.</para>
</section>
</section>
</chapter>

19
spring-framework-reference/src/testing.xml
View File

@ -993,7 +993,7 @@ public void testProcessRepeatedly() {
<listitem>
<para><interfacename>ContextLoader</interfacename>: Strategy
interface for loading an
interface introduced in Spring 2.5 for loading an
<interfacename>ApplicationContext</interfacename> for an
integration test managed by the Spring TestContext
Framework.</para>
@ -1028,7 +1028,7 @@ public void testProcessRepeatedly() {
<classname>AnnotationConfigContextLoader</classname> or a
<classname>GenericXmlContextLoader</classname> depending
either on the configuration declared for the test class or on
the presence of default locations or configuration
the presence of default locations or default configuration
classes.</para>
</listitem>
@ -1039,8 +1039,8 @@ public void testProcessRepeatedly() {
</listitem>
<listitem>
<para><classname>GenericXmlContextLoader</classname>: loads
and application context from XML resource locations.</para>
<para><classname>GenericXmlContextLoader</classname>: loads an
application context from XML resource locations.</para>
</listitem>
<listitem>
@ -1151,8 +1151,8 @@ public class MyTest {
<para><interfacename>@ContextConfiguration</interfacename> supports
an alias for the <literal>locations</literal> attribute through the
standard <literal>value</literal> attribute. Thus, if you do not
need to configure a custom
standard Java <literal>value</literal> attribute. Thus, if you do
not need to configure a custom
<interfacename>ContextLoader</interfacename>, you can omit the
declaration of the <literal>locations</literal> attribute name and
declare the resource locations by using the shorthand format
@ -1345,9 +1345,10 @@ public class ExtendedTest extends BaseTest {
linkend="integration-testing-annotations-spring" />). This instructs
Spring to reload the configuration and rebuild the application
context before executing the next test. Note that support for the
<interfacename>@DirtiesContext</interfacename> annotation is enabled
via the <classname>DirtiesContextTestExecutionListener</classname>
which is enabled by default.</para>
<interfacename>@DirtiesContext</interfacename> annotation is
provided by the
<classname>DirtiesContextTestExecutionListener</classname> which is
enabled by default.</para>
</section>
</section>