From 223e1e4522a95400edda857e12df10a000576fac Mon Sep 17 00:00:00 2001 From: Keith Donald Date: Thu, 3 Sep 2009 14:44:10 +0000 Subject: [PATCH] polish --- spring-framework-reference/src/validation.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/spring-framework-reference/src/validation.xml b/spring-framework-reference/src/validation.xml index 04357496dc7..22306a1235b 100644 --- a/spring-framework-reference/src/validation.xml +++ b/spring-framework-reference/src/validation.xml @@ -805,7 +805,7 @@ public interface ConverterFactory { Parameterize S to be type you are converting from, and R to be base type defining the range of classes you can convert to. - Then implement getConverter(Class<T>T), where T is a subclass of R. + Then implement getConverter(Class<T>), where T is a subclass of R. Note the StringToEnum ConverterFactory as an example: @@ -861,7 +861,7 @@ public interface ConversionService {
Configuring a ConversionService - A ConversionService is a stateless object designed to be instantiated on application startup, then shared between multiple threads. + A ConversionService is a stateless object designed to be instantiated at application startup, then shared between multiple threads. In a Spring application, you typically configure a ConversionService instance per Spring container (or ApplicationContext). That ConversionService will be picked up by Spring and then used whenever a type conversion needs to be performed by the framework. You may also inject this ConversionService into any of your beans and invoke it directly. @@ -919,7 +919,7 @@ public class MyService { Now consider the type conversion requirements of a typical UI environment such as a web or desktop application. - In such environments, you typically convert from String to support the postback process, as well as back to String to support the rendering process. + In such environments, you typically convert from String to support the form postback process, as well as back to String to support the rendering process. The more general core.convert system does not address this specific scenario directly. To directly address this, Spring 3 introduces a new ui.format system that provides a simple and robust alternative to PropertyEditors in a UI environment.