lasses = [WebConfig::class])) class WebIntegrationTests { // class body... } If you need to merge or override the configuration for a given level of the context hierarchy within a test class hierarchy @Sql declarations. If @SqlMergeMode is not declared on a test class or test method, the OVERRIDE merge mode will be used by default. With the OVERRIDE mode, method-level @Sql declarations will effectively @SqlMergeMode(MERGE) ① class UserTests { @Test @Sql("/user-test-data-001.sql") void standardUserProfile() { // run code that relies on test data set 001 } } ① Set the @Sql merge mode to

reworked AbstractBeanFactory's bean definition merging for less coupling to RootBeanDefinition as merge result * introduced GenericBeanDefinition as one-stop shop for standard bean definition purposes * deprecated HibernateTemplate's "saveOrUpdateAll" method in favor of individual "saveOrUpdate"/"merge" usage * fixed Hibernate/JpaTransactionManager to clean up properly in case of transaction begin failure collection as-is in this case * indexed constructor arguments support collection merging (driven by merge="true", analogous to property values) * BeanDefinitions returned by nested custom XML elements receive

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute

id="child" parent="parent"> merge="true"> sales@somecompany.com support@somecompany.co.uk Notice the use of the merge=true attribute on the element of the adminEmails property of the child bean definition. When you cannot merge different collection types (e.g. a Map and a List), and if you do attempt to do so an appropriate Exception will be thrown; and in case it is not immediately obvious, the 'merge' attribute