Introduced StandardScriptFactory as a JSR-223 based mechanism for scripted beans, exposed through the lang:std element in XML. Supports e.g. JavaScript and JRuby. (Note: JRubyScriptFactory and lang:jruby are deprecated invoked handler methods. Client-side REST test support allows indicating how many times a request is expected and whether the order of declaration for expectations should be ignored (see the section called candidates within the container that match the expected type are provided to satisfy the dependency. You can autowire strongly- typed Maps if the expected key type is String. An autowired Maps values will

Introduced StandardScriptFactory as a JSR-223 based mechanism for scripted beans, exposed through the lang:std element in XML. Supports e.g. JavaScript and JRuby. (Note: JRubyScriptFactory and lang:jruby are deprecated invoked handler methods. Client-side REST test support allows indicating how many times a request is expected and whether the order of declaration for expectations should be ignored (see the section called candidates within the container that match the expected type are provided to satisfy the dependency. You can autowire strongly- typed Maps if the expected key type is String. An autowired Maps values will

Introduced StandardScriptFactory as a JSR-223 based mechanism for scripted beans, exposed through the lang:std element in XML. Supports e.g. JavaScript and JRuby. (Note: JRubyScriptFactory and lang:jruby are deprecated handler methods. • Client-side REST test support allows indicating how many times a request is expected and whether the order of declaration for expectations should be ignored (see the section called candidates within the container that match the expected type are provided to satisfy the dependency. You can autowire strongly-typed Maps if the expected key type is String. An autowired Maps values will

Introduced StandardScriptFactory as a JSR-223 based mechanism for scripted beans, exposed through the lang:std element in XML. Supports e.g. JavaScript and JRuby. (Note: JRubyScriptFactory and lang:jruby are deprecated handler methods. • Client-side REST test support allows indicating how many times a request is expected and whether the order of declaration for expectations should be ignored (see the section called candidates within the container that match the expected type are provided to satisfy the dependency. You can autowire strongly-typed Maps if the expected key type is String. An autowired Maps values will

corresponding element: • (Groovy) • (BeanShell) • std/> (JSR-223, e.g. with JRuby) The exact attributes and child elements that are available for configuration

corresponding element: • (Groovy) • (BeanShell) • std/> (JSR-223, e.g. with JRuby) The exact attributes and child elements that are available for configuration

test instance. Within our sessionScope() test method, we set up our test fixture by setting the expected theme attribute in the provided MockHttpSession. When the processUserPreferences() method is invoked jdbcTemplate, tableName); } private void assertNumUsers(int expected) { assertEquals("Number of rows in the [user] table.", expected, countRowsInTable("user")); } } 108 Kotlin @SpringJU mplate, tableName) } private fun assertNumUsers(expected: Int) { assertEquals("Number of rows in the [user] table.", expected, countRowsInTable("user")) } } As explained in Transaction

things the non-blocking way and that can slightly increase the required processing time. The key expected benefit of reactive and non-blocking is the ability to scale with a small, fixed 5 number of threads original raw content can no longer be read from the request body. For this reason, applications are expected to go through ServerWebExchange consistently for access to the cached form data versus reading request body) to be resolved. This is marked in the Description column. Reactive types are not expected on arguments that do not require blocking. JDK 1.8’s java.util.Optional is supported as a method

been called, see Spring Boot application lifecycle and related Application Events. TIP Tasks expected to run during startup should be executed by CommandLineRunner and ApplicationRunner components Configuration tree values can be bound to both string String and byte[] types depending on the contents expected. If you have multiple config trees to import from the same parent folder you can use a wildcard using Maven or Gradle or from its packaged jar. This can cause Spring Boot to fail to find the expected template. If you have this problem, you can reorder the classpath in the IDE to place the module’s

been called, see Spring Boot application lifecycle and related Application Events. TIP Tasks expected to run during startup should be executed by CommandLineRunner and ApplicationRunner components Configuration tree values can be bound to both string String and byte[] types depending on the contents expected. If you have multiple config trees to import from the same parent folder you can use a wildcard using Maven or Gradle or from its packaged jar. This can cause Spring Boot to fail to find the expected template. If you have this problem, you can reorder the classpath in the IDE to place the module’s