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

fixed typos 

git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@2793 50f2f4bb-b051-0410-bef5-90022cba6387
This commit is contained in:
Juergen Hoeller 2010-01-08 15:47:20 +00:00
parent 8225c29b39
commit 79137352f5
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
spring-framework-reference/src/mvc.xml
View File

@ -16,7 +16,7 @@
wide range of flexible handling methods. With the introduction of Spring
3.0, the <interfacename>@Controller</interfacename> mechanism also allows
you to create RESTful Web sites and applications, through the
<interfacename>@PathVarariable</interfacename> annotation and other
<interfacename>@PathVariable</interfacename> annotation and other
features.</para>
<sidebar id="mvc-open-for-extension">

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

@ -1652,17 +1652,17 @@ code, etc? Or what? If my rewording is wrong, revise to clarify. What does using
<para>The <emphasis>Spring TestContext Framework</emphasis> offers
full integration with JUnit 4.5+ through a custom runner (tested on
JUnit 4.5, 4.6, and 4.7). By annotating test classes with
<literal>@Runwith(SpringJUnit4ClassRunner.class)</literal>,
<literal>@RunWith(SpringJUnit4ClassRunner.class)</literal>,
developers can implement standard JUnit 4.5+ unit and integration
tests and simultaneously reap the benefits of the TestContext
framework such as support for loading application contexts,
dependency injection of test instances, transactional test method
execution, and so on. The following code listing displays the
minimal requirements for configuring a test class to run with the
custom Spring Runner. @TestExecutionListeners is configured with an
empty list in order to disable the default listeners, which
otherwise would require an ApplicationContext to be configured
through @ContextConfiguration.</para>
execution, and so on. The following code listing displays the minimal
requirements for configuring a test class to run with the custom Spring
Runner. <interfacename>@TestExecutionListeners</interfacename> is
configured with an empty list in order to disable the default listeners,
which otherwise would require an ApplicationContext to be configured
through <interfacename>@ContextConfiguration</interfacename>.</para>
<programlisting language="java">@RunWith(SpringJUnit4ClassRunner.class)
@TestExecutionListeners({})