Affects Version/s: 3.1.1
Fix Version/s: None
Last commented by a User:true
The issue could be revealed if MyBatis for Spring is used.
MapperScannerConfigurer in MyBatis for Spring v1.1.0+ has changed to use BeanDefinitionRegistryPostProcessor instead of BeanFactoryPostProcessor as of v1.0.x for scanning MyBatis mapper resources.
The case is postProcessBeanDefinitionRegistry(BeanDefinitionRegistry beanDefinitionRegistry) is not called by Spring container if MapperScannerConfigurer is created through @Bean (but it will be called if the bean is created through XML configuration)
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Duplicate [ 3 ]|
|Assignee||Chris Beams [ cbeams ]|
|Workflow||SPR Workflow [ 53695 ]||New SPR Workflow [ 57160 ]|
|Workflow||New SPR Workflow [ 57160 ]||SPR Workflow [ 66226 ]|