also possible to have a context hierarchy where one root WebApplicationContext is shared across multiple DispatcherServlet (or other Servlet) instances, each with its own child WebApplicationContext infrastructure beans, such as data repositories and business services that need to be shared across multiple Servlet instances. Those beans are effectively inherited and can be overridden (that is, re-declared) can be found. The string consists potentially of multiple strings (using a comma as a delimiter) to support multiple contexts. In the case of multiple context locations with beans that are defined twice

to dependency inject domain objects with Spring Unit testing @Configurable objects Working with multiple application contexts Other Spring aspects for AspectJ Configuring AspectJ aspects using Spring semantics for different beans settings Using @Transactional @Transactional settings Multiple Transaction Managers with @Transactional Custom shortcut annotations Transaction propagation Required batch operations with the JdbcTemplate Batch operations with a List of objects Batch operations with multiple batches Simplifying JDBC operations with the SimpleJdbc classes Inserting data using SimpleJdbcInsert

to dependency inject domain objects with Spring Unit testing @Configurable objects Working with multiple application contexts Other Spring aspects for AspectJ Configuring AspectJ aspects using Spring semantics for different beans settings Using @Transactional @Transactional settings Multiple Transaction Managers with @Transactional Custom shortcut annotations Transaction propagation Required batch operations with the JdbcTemplate Batch operations with a List of objects Batch operations with multiple batches Simplifying JDBC operations with the SimpleJdbc classes Inserting data using SimpleJdbcInsert

@Configurable objects .......................................................... 256 Working with multiple application contexts ................................................ 256 Other Spring aspects for @Transactional settings .......................................................................... 392 Multiple Transaction Managers with @Transactional ................................. 393 Custom shortcut objects ............................................................. 423 Batch operations with multiple batches ............................................................ 424 19.5. Simplifying JDBC

@Configurable objects .......................................................... 249 Working with multiple application contexts ................................................ 249 Other Spring aspects for @Transactional settings .......................................................................... 384 Multiple Transaction Managers with @Transactional ................................. 385 Custom shortcut objects ............................................................. 416 Batch operations with multiple batches ............................................................ 417 19.5. Simplifying JDBC

remains completely unchanged. It is often the case that a single set of profiles is used across multiple test classes within a given project. Thus, to avoid duplicate declarations of the @ActiveProfiles @TestPropertySource can be used as repeatable annotation. That means that you can have multiple declarations of @TestPropertySource on a single test class, with the locations and properties overriding those from previous @TestPropertySource annotations. In addition, you may declare multiple composed annotations on a test class that are each meta-annotated with @TestPropertySource

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Working with Multiple Application Contexts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependencies. Composing XML-based Configuration Metadata It can be useful to have bean definitions span multiple XML files. Often, each individual XML configuration file represents a logical layer or module in context constructor to load bean definitions from all these XML fragments. This constructor takes multiple Resource locations, as was shown in the previous section. Alternatively, use one or more occurrences

Default Import Statements Automatic Main Method Custom Dependency Management Applications with Multiple Source Files Packaging Your Application Initialize a New Project Using the Embedded Shell Adding Tomcat’s Proxy Configuration Configure Tomcat Enable Multiple Connectors with Tomcat Use Tomcat’s LegacyCookieProcessor Configure Undertow Enable Multiple Listeners with Undertow Create WebSocket Endpoints Installation with SDKMAN! SDKMAN! (The Software Development Kit Manager) can be used for managing multiple versions of various binary SDKs, including Groovy and the Spring Boot CLI. Get SDKMAN! from sdkman

Default Import Statements Automatic Main Method Custom Dependency Management Applications with Multiple Source Files Packaging Your Application Initialize a New Project Using the Embedded Shell Adding Proxy Server Customize Tomcat’s Proxy Configuration Enable Multiple Connectors with Tomcat Use Tomcat’s LegacyCookieProcessor Enable Multiple Listeners with Undertow Create WebSocket Endpoints Using @ServerEndpoint Installation with SDKMAN! SDKMAN! (The Software Development Kit Manager) can be used for managing multiple versions of various binary SDKs, including Groovy and the Spring Boot CLI. Get SDKMAN! from sdkman

Default Import Statements Automatic Main Method Custom Dependency Management Applications with Multiple Source Files Packaging Your Application Initialize a New Project Using the Embedded Shell Adding Proxy Server Customize Tomcat’s Proxy Configuration Enable Multiple Connectors with Tomcat Use Tomcat’s LegacyCookieProcessor Enable Multiple Listeners with Undertow Create WebSocket Endpoints Using @ServerEndpoint Installation with SDKMAN! SDKMAN! (The Software Development Kit Manager) can be used for managing multiple versions of various binary SDKs, including Groovy and the Spring Boot CLI. Get SDKMAN! from sdkman