Correct typos: ch 19 [SPR-7159] #11818
Description
Cristian George Rapauzu opened SPR-7159 and commented
Document URL: http://static.springsource.org/spring/docs/current/spring-framework-reference/html/
Spring 3.0 - Chapter 19. Remoting and web services using Spring
Location: 19.1 Introduction
Problem: Confusing text: "four remoting technologies:" is followed by six same-level bullets
Text: Currently, Spring supports four remoting technologies: ...
Suggestion: Restructure list:
- RMI
- HTTP-based
2.1. HTTP Invoker
2.2. Hessian
2.3. Burlap - Web Services
3.1. JAX-RPC
3.2. JAX-WS - JMS
Location: 19.3.1 Wiring up the DispatcherServlet for Hessian and co.
Problem: Missing word "is": "this an excerpt from" instead of "this is an excerpt from"
Text: this an excerpt from 'web.xml'
Suggestion: Consistency - use filename as title for all code samples
(web.xml , WEB-INF/applicationContext.xml, remoting-servlet.xml)
Location: 19.3.5 Applying HTTP basic authentication to a service exposed through Hessian or Burlap
Problem: Missing word "is": "This an example" instead of "This is an example"
Text: This an example where we explicitly mention the BeanNameUrlHandlerMapping and ...
Location: 19.4 Exposing services using HTTP invokers
Problem: Inconsistent case usage for HTTP: "Spring Http invokers" instead of "Spring HTTP invokers"
Text: Spring Http invokers use the standard Java serialization mechanism to expose services through HTTP ...
Location: 19.4.1 Exposing the service object
Problem: Typo - extra char "s": "for a service objects" instead of "for a service object"
Text: Setting up the HTTP invoker infrastructure for a service objects much resembles the way you would do using Hessian or Burlap.
Location: 19.4.1 Exposing the service object
Problem: Typo - missing char "I": "f you are running" instead of "If you are running"
Text: f you are running outside of a servlet container and are using ...
Location: 19.4.1 Exposing the service object
Problem: Inconsistent text style usage for class names (SimpleHttpServerFactoryBean, SimpleHttpInvokerServiceExporter): normal text instead of fixed-width text
Text: You can configure the SimpleHttpServerFactoryBean together with a SimpleHttpInvokerServiceExporter as is shown in this example
Location: 19.5.2 Accessing web services using JAX-RPC
Problem: Typo - missing char "t": "this a startup time" instead of "this at startup time"
Text: Spring needs this a startup time to create the JAX-RPC Service.
Location: 19.5.8 Accessing web services using JAX-WS
Problem: Typo - missing char "t": "this a startup time" instead of "this at startup time"
Text: Spring needs this a startup time to create the JAX-WS Service.
Location: 19.5.9 Exposing web services using XFire
Problem: Missing word "is": "context that shipping" instead of "context that is shipping"
Text: Exposing XFire is done using a XFire context that shipping with XFire itself in combination with a RemoteExporter-style bean you have to add to your WebApplicationContext.
Location: 19.8 Considerations when choosing a technology
Problem: Typo - missing char "r": "consider you needs" instead of "consider your needs"
Text: You should carefully consider you needs, the services your exposing and the objects you'll be sending over the wire when choosing a technology.
Location: 19.8 Considerations when choosing a technology
Problem: Typo: "the services your exposing" instead of "the services you are exposing"
Text: You should carefully consider you needs, the services your exposing and the objects you'll be sending over the wire when choosing a technology.
Location: 19.8 Considerations when choosing a technology
Problem: Typo - missing char "s": "it support" instead of "it supports"
Text: RMI is a fairly heavy-weight protocol in that it support full-object serialization which is important when using a complex data model that needs serialization over the wire.
Location: 19.9.1 RestTemplate
Problem: Typo - missing char "." to break in two phrases: "RestClientException will be thrown, this behavior can be changed" instead of "RestClientException will be thrown. This behavior can be changed"
Text: In case of an exception processing the HTTP request, an exception of the type RestClientException will be thrown, this behavior can be changed by plugging in another ResponseErrorHandler implementation into the RestTemplate.
Location: 19.9.1.1 Dealing with request and response headers
Problem: Typo (probably) - text mentions "execute method", but code mentions "exchange" method
Text: Besides the methods described above, the RestTemplate also has the exchange method, which can be used for arbitrary HTTP method execution based on the HttpEntity class. Perhaps most importantly, the execute method can be used to add request headers and read response headers. For example:
... HttpEntity<String> response = template.exchange(...)
Affects: 3.0.1
Referenced from: commits a45d33a