Remove duplicate words
Closes gh-1039
This commit is contained in:
committed by
Stephane Nicoll
parent
50c11028d5
commit
44e652f99e
@@ -1317,7 +1317,7 @@ See <<mvc-config-conversion>> in the Spring MVC chapter.
|
||||
[[format-configuring-formatting-globaldatetimeformat]]
|
||||
== Configuring a global date & time format
|
||||
By default, date and time fields that are not annotated with `@DateTimeFormat` are
|
||||
converted from strings using the the `DateFormat.SHORT` style. If you prefer, you can
|
||||
converted from strings using the `DateFormat.SHORT` style. If you prefer, you can
|
||||
change this by defining your own global format.
|
||||
|
||||
You will need to ensure that Spring does not register default formatters, and instead
|
||||
|
||||
@@ -3435,7 +3435,7 @@ The batch update methods for this call returns an array of int arrays containing
|
||||
entry for each batch with an array of the number of affected rows for each update. The top
|
||||
level array's length indicates the number of batches executed and the second level array's
|
||||
length indicates the number of updates in that batch. The number of updates in each batch
|
||||
should be the the batch size provided for all batches except for the last one that might
|
||||
should be the batch size provided for all batches except for the last one that might
|
||||
be less, depending on the total number of update objects provided. The update count for
|
||||
each update statement is the one reported by the JDBC driver. If the count is not
|
||||
available, the JDBC driver returns a -2 value.
|
||||
|
||||
@@ -260,7 +260,7 @@ container-managed transactions. All your custom business logic can be implemente
|
||||
simple POJOs and managed by Spring's IoC container. Additional services include support
|
||||
for sending email and validation that is independent of the web layer, which lets you
|
||||
choose where to execute validation rules. Spring's ORM support is integrated with JPA,
|
||||
Hibernate and and JDO; for example, when using Hibernate, you can continue to use
|
||||
Hibernate and JDO; for example, when using Hibernate, you can continue to use
|
||||
your existing mapping files and standard Hibernate `SessionFactory` configuration. Form
|
||||
controllers seamlessly integrate the web-layer with the domain model, removing the need
|
||||
for `ActionForms` or other classes that transform HTTP parameters to values for your
|
||||
|
||||
@@ -3592,7 +3592,7 @@ manual, the javadocs for `@SqlConfig` and `SqlScriptsTestExecutionListener` prov
|
||||
detailed information, and the following example demonstrates a typical testing scenario
|
||||
using JUnit and transactional tests with `@Sql`. Note that there is no need to clean up
|
||||
the database after the `usersTest()` method is executed since any changes made to the
|
||||
database (either within the the test method or within the `/test-data.sql` script) will
|
||||
database (either within the test method or within the `/test-data.sql` script) will
|
||||
be automatically rolled back by the `TransactionalTestExecutionListener` (see
|
||||
<<testcontext-tx,transaction management>> for details).
|
||||
|
||||
|
||||
@@ -1300,7 +1300,7 @@ multiple requests are allowed to access a session concurrently.
|
||||
methods and/or the HandlerAdapter configuration. See the `webBindingInitializer`
|
||||
property on `RequestMappingHandlerAdapter`. Such command objects along with their
|
||||
validation results will be exposed as model attributes by default, using the command
|
||||
class class name - e.g. model attribute "orderAddress" for a command object of type
|
||||
class name - e.g. model attribute "orderAddress" for a command object of type
|
||||
"some.package.OrderAddress". The `ModelAttribute` annotation can be used on a method
|
||||
argument to customize the model attribute name used.
|
||||
* `org.springframework.validation.Errors` /
|
||||
@@ -1685,7 +1685,7 @@ Given the above example where can the Pet instance come from? There are several
|
||||
more detail below).
|
||||
* It may be instantiated using its default constructor.
|
||||
|
||||
An `@ModelAttribute` method is a common way to to retrieve an attribute from the
|
||||
An `@ModelAttribute` method is a common way to retrieve an attribute from the
|
||||
database, which may optionally be stored between requests through the use of
|
||||
`@SessionAttributes`. In some cases it may be convenient to retrieve the attribute by
|
||||
using an URI template variable and a type converter. Here is an example:
|
||||
@@ -3929,7 +3929,7 @@ raised the status code may indicate a client error (4xx) or a server error (5xx)
|
||||
|
||||
The `DefaultHandlerExceptionResolver` translates Spring MVC exceptions to specific error
|
||||
status codes. It is registered by default with the MVC namespace, the MVC Java config,
|
||||
and also by the the `DispatcherServlet` (i.e. when not using the MVC namespace or Java
|
||||
and also by the `DispatcherServlet` (i.e. when not using the MVC namespace or Java
|
||||
config). Listed below are some of the exceptions handled by this resolver and the
|
||||
corresponding status codes:
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ is another view technology, supported by Spring. This template engine is a templ
|
||||
aimed at generating XML-like markup (XML, XHTML, HTML5, ...), but that can be used to generate any
|
||||
text based content.
|
||||
|
||||
This requires Groovy 2.3.1+ on the the classpath.
|
||||
This requires Groovy 2.3.1+ on the classpath.
|
||||
|
||||
[[view-groovymarkup-configuration]]
|
||||
=== Configuration
|
||||
|
||||
Reference in New Issue
Block a user