Event Listeners Asynchronous Listeners Ordering Listeners Generic Events Convenient access to low-level resources Convenient ApplicationContext instantiation for web applications Deploying a Spring ApplicationContext framework TestExecutionListener configuration Registering custom TestExecutionListeners Automatic discovery of default TestExecutionListeners Ordering TestExecutionListeners Merging TestExecutionListeners transaction abstraction Synchronizing resources with transactions High-level synchronization approach Low-level synchronization approach TransactionAwareDataSourceProxy Declarative transaction management Understanding

event listeners Asynchronous Listeners Ordering listeners Generic events Convenient access to low-level resources Convenient ApplicationContext instantiation for web applications Deploying a Spring ApplicationContext framework TestExecutionListener configuration Registering custom TestExecutionListeners Automatic discovery of default TestExecutionListeners Ordering TestExecutionListeners Merging TestExecutionListeners transaction abstraction Synchronizing resources with transactions High-level synchronization approach Low-level synchronization approach TransactionAwareDataSourceProxy Declarative transaction management Understanding

..................................................................... 150 Convenient access to low-level resources ........................................................ 151 Convenient ApplicationContext . 304 Spring Framework Reference Documentation 4.3.2.RELEASE Spring Framework xii Automatic discovery of default TestExecutionListeners .............................. 304 Ordering TestExecutionListeners High-level synchronization approach ................................................................ 368 Low-level synchronization approach ................................................................. 369

.................................................................... 157 Convenient access to low-level resources ........................................................ 158 Convenient ApplicationContext Registering custom TestExecutionListeners .............................................. 311 Automatic discovery of default TestExecutionListeners .............................. 311 Ordering TestExecutionListeners High-level synchronization approach ................................................................ 375 Low-level synchronization approach ................................................................. 376

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot ler and register a bean definition of that type. Because an ErrorWebExceptionHandler is quite low-level, Spring Boot also provides a convenient AbstractErrorWebExceptionHandler to let you handle errors

Implementations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Automatic Discovery of Default TestExecutionListener Implementations . . . . . . . . . . . . . . . . . 48 Ordering classes. If you wish to register a listener globally, you should register it via the automatic discovery mechanism described in TestExecutionListener Configuration. The following example shows how to sets of ContextCustomizerFactory and TestExecutionListener implementations, and so on. For such low-level control over how the TestContext framework operates, Spring provides a bootstrapping strategy.

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot ler and register a bean definition of that type. Because an ErrorWebExceptionHandler is quite low-level, Spring Boot also provides a convenient AbstractErrorWebExceptionHandler to let you handle errors

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot ler and register a bean definition of that type. Because an ErrorWebExceptionHandler is quite low-level, Spring Boot also provides a convenient AbstractErrorWebExceptionHandler to let you handle errors

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot ler and register a bean definition of that type. Because an ErrorWebExceptionHandler is quite low-level, Spring Boot also provides a convenient AbstractErrorWebExceptionHandler to let you handle errors

until an HTTP request is received. A downside of lazy initialization is that it can delay the discovery of a problem with the application. If a misconfigured bean is initialized lazily, a failure will @ServletComponentScan has no effect in a standalone container, where the container’s built-in discovery mechanisms are used instead. The ServletWebServerApplicationContext Under the hood, Spring Boot ler and register a bean definition of that type. Because an ErrorWebExceptionHandler is quite low-level, Spring Boot also provides a convenient AbstractErrorWebExceptionHandler to let you handle errors