Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typos, formatting and escaping in reference

Browse Source 
Note: Some symbol combinations (including <=) serve as textual symbol
replacements in AsciiDoc.

http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#text-replacement
This commit is contained in:
Bian Jiaping
2017-11-20 10:00:54 +08:00
committed by Rossen Stoyanchev
parent 22a8a668c9
commit 8f525f07e9
6 changed files with 27 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/docs/asciidoc/web/webmvc-view.adoc
View File

@@ -209,7 +209,7 @@ generation (including validation error display). It is never necessary to use th
macros to generate form input fields, and they can be mixed and matched with simple HTML
or calls direct to the spring bind macros highlighted previously.
The following table of available macros show the VTL and FTL definitions and the
The following table of available macros show the FTL definitions and the
parameter list that each takes.
[[views-macros-defs-tbl]]
@@ -262,9 +262,9 @@ parameter list that each takes.
| <@spring.showErrors separator, classOrStyle/>
|===
* In FTL (FreeMarker), these two macros are not actually required as you can use the
normal `formInput` macro, specifying ' `hidden`' or ' `password`' as the value for the
`fieldType` parameter.
* In FTL (FreeMarker), `formHiddenInput` and `formPasswordInput` are not actually required
as you can use the normal `formInput` macro, specifying `hidden` or `password` as the
value for the `fieldType` parameter.
The parameters to any of the above macros have consistent meanings:
@@ -420,14 +420,14 @@ your model where they will be visible to your templates). The advantage of speci
them in the templates is that they can be changed to different values later in the
template processing to provide different behavior for different fields in your form.
To switch to XHTML compliance for your tags, specify a value of 'true' for a
To switch to XHTML compliance for your tags, specify a value of `true` for a
model/context variable named xhtmlCompliant:
[source,jsp,indent=0]
[subs="verbatim,quotes"]
----
<#-- for FreeMarker -->
<#assign xhtmlCompliant = true in spring>
<#assign xhtmlCompliant = true>
----
Any tags generated by the Spring macros will now be XHTML compliant after processing
@@ -435,12 +435,12 @@ this directive.
In similar fashion, HTML escaping can be specified per field:
[source,xml,indent=0]
[source,jsp,indent=0]
[subs="verbatim,quotes"]
----
<#-- until this point, default HTML escaping is used -->
<#assign htmlEscape = true in spring>
<#assign htmlEscape = true>
<#-- next field will use HTML escaping -->
<@spring.formInput "command.name"/>

15
src/docs/asciidoc/web/webmvc.adoc
View File

@@ -479,7 +479,7 @@ initialization parameters ( `init-param` elements) to the Servlet declaration in
All `HandlerMapping` implementations supports handler interceptors that are useful when
you want to apply specific functionality to certain requests, for example, checking for
a principal. Interceptors must implement `HandlerInterceptor` from the
`org.springframework .web .servlet` package with three methods that should provide enough
`org.springframework.web.servlet` package with three methods that should provide enough
flexibility to do all kinds of pre-processing and post-processing:
* `preHandle(..)` -- __before__ the actual handler is executed
@@ -498,7 +498,7 @@ configure interceptors. You can also register them directly via setters on indiv
`HandlerMapping` implementations.
Note that `postHandle` is less useful with `@ResponseBody` and `ResponseEntity` methods for
which a the response is written and committed within the `HandlerAdapter` and before
which the response is written and committed within the `HandlerAdapter` and before
`postHandle`. That means its too late to make any changes to the response such as adding
an extra header. For such scenarios you can implement `ResponseBodyAdvice` and either
declare it as an <<mvc-ann-controller-advice>> bean or configure it directly on
@@ -2543,8 +2543,8 @@ on a container object that specifies request headers and body. Below is an examp
@PostMapping("/something")
public ResponseEntity<String> handle() {
// ...
URI location = ...
return new ResponseEntity.created(location).build();
URI location = ... ;
return ResponseEntity.created(location).build();
}
----
@@ -4167,8 +4167,7 @@ And the same in XML use the `<mvc:view-controller>` element:
The MVC config simplifies the registration of view resolvers.
The following is a Java config example that configures content negotiation view
resolution using FreeMarker HTML templates and Jackson as a default `View` for
JSON rendering:
resolution using JSP and Jackson as a default `View` for JSON rendering:
[source,java,indent=0]
[subs="verbatim,quotes"]
@@ -4296,8 +4295,8 @@ See also
<<mvc-caching-static-resources, HTTP caching support for static resources>>.
The resource handler also supports a chain of
{api-spring-framework}/web/servlet/resource/ResourceResolver.html[ResourceResolver]'s and
{api-spring-framework}/web/servlet/resource/ResourceTransformer.html[ResourceTransformer]'s.
{api-spring-framework}/web/servlet/resource/ResourceResolver.html[ResourceResolver]s and
{api-spring-framework}/web/servlet/resource/ResourceTransformer.html[ResourceTransformer]s.
which can be used to create a toolchain for working with optimized resources.
The `VersionResourceResolver` can be used for versioned resource URLs based on an MD5 hash