was UTF-8) * RedirectView considers arrays and collections with eligible values, turning them into multi-value request parameters * RedirectView accepts StringBuffers, StringBuilders, Numbers, Dates, URIs well Package org.springframework.test * "executeSqlScript" (as in SimpleJdbcTestUtils) allows for multi-line statements, each separated by a semicolon Package org.springframework.transaction * Transa @Controller beans by default as well * ControllerClassNameHandlerMapping registers plain path for multi-action controllers too ("/welcome/*" + "/welcome") * added ControllerBeanNameHandlerMapping, deriving

was UTF-8) * RedirectView considers arrays and collections with eligible values, turning them into multi-value request parameters * RedirectView accepts StringBuffers, StringBuilders, Numbers, Dates, URIs well Package org.springframework.test * "executeSqlScript" (as in SimpleJdbcTestUtils) allows for multi-line statements, each separated by a semicolon Package org.springframework.transaction * Transa @Controller beans by default as well * ControllerClassNameHandlerMapping registers plain path for multi-action controllers too ("/welcome/*" + "/welcome") * added ControllerBeanNameHandlerMapping, deriving

was UTF-8) * RedirectView considers arrays and collections with eligible values, turning them into multi-value request parameters * RedirectView accepts StringBuffers, StringBuilders, Numbers, Dates, URIs well Package org.springframework.test * "executeSqlScript" (as in SimpleJdbcTestUtils) allows for multi-line statements, each separated by a semicolon Package org.springframework.transaction * Transa @Controller beans by default as well * ControllerClassNameHandlerMapping registers plain path for multi-action controllers too ("/welcome/*" + "/welcome") * added ControllerBeanNameHandlerMapping, deriving

decoding to a single-value publisher (e.g. Mono), there is one TokenBuffer. • When decoding to a multi-value publisher (e.g. Flux), each TokenBuffer is passed to the ObjectMapper as soon as enough bytes ObjectMapper. • For a multi-value publisher with application/json, by default collect the values with Flux#collectToList() and then serialize the resulting collection. • For a multi-value publisher with model. Single-value reactive types are resolved to a single value or no value (if empty), while multi-value reactive types (for example, Flux) are collected and resolved to List. To configure

constructor-based approach as well, since you may wish to use it with pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor serious issues (potentially resulting in memory leaks) when incorrectly using them in a multi-threaded and multi-classloader environments. One should always consider wrapping a threadlocal in some other SmartDataSource that wraps a single connection which is not closed after use. Obviously, this is not multi-threading capable. If client code will call close in the assumption of a pooled connection, like

well Package org.springframework.test * "executeSqlScript" (as in SimpleJdbcTestUtils) allows for multi-line statements, each separated by a semicolon Package org.springframework.transaction * Transa @Controller beans by default as well * ControllerClassNameHandlerMapping registers plain path for multi-action controllers too ("/welcome/*" + "/welcome") * added ControllerBeanNameHandlerMapping, deriving into spring-webmvc- struts.jar * Spring-style pattern matching ("*xxx", "xxx*", "*xxx*") supports multi-part patterns as well now ("xxx*yyy") Package org.springframework.aop * ProxyFactoryBean and Ab

example, to offer personalized layouts. See Themes. MultipartResolver Abstraction for parsing a multi-part request (for example, browser form file upload) with the help of some multipart parsing library ReactiveAdapterRegistry A single value type, e.g. Mono, is comparable to returning DeferredResult. A multi-value type, e.g. Flux, may be treated as a stream depending on the requested media type, e.g. "text/event- using a single value reactive type to produce the ResponseEntity asynchronously, and/or single and multi-value reactive types for the body. This allows the following types of async responses: • ResponseEntity>

constructor-based approach as well, since you may wish to use it with pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor serious issues (potentially resulting in memory leaks) when incorrectly using them in a multi-threaded and multi-classloader environments. One should always consider wrapping a threadlocal in some other SmartDataSource that wraps a single connection which is not closed after use. Obviously, this is not multi-threading capable. If client code will call close in the assumption of a pooled connection, like

constructor-based approach as well, since you may wish to use it with pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor serious issues (potentially resulting in memory leaks) when incorrectly using them in a multi-threaded and multi-classloader environments. One should always consider wrapping a threadlocal in some other SmartDataSource that wraps a single connection which is not closed after use. Obviously, this is not multi-threading capable. If client code will call close in the assumption of a pooled connection, like

constructor-based approach as well, since you may wish to use it with pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor serious issues (potentially resulting in memory leaks) when incorrectly using them in a multi-threaded and multi-classloader environments. One should always consider wrapping a threadlocal in some other SmartDataSource that wraps a single connection which is not closed after use. Obviously, this is not multi-threading capable. If client code will call close in the assumption of a pooled connection, like