[SHIRO-732] Configuration conflict

• Type: Question
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.2
• Component/s: Configuration
• Assignee: Unassigned
• Reporter: jiahua_lan
• Created: 08/Dec/19 16:21
• Updated: 16/Dec/19 15:55

Description

When I used shiro-spring-boot-web-starter, I found that the configuration of both org.apache.shiro.spring.web.config.ShiroWebConfiguration and org.apache.shiro.spring.config.web.autoconfigure.ShiroWebAutoConfiguration seems to be Conflict with each other. One bean is defined in org.apache.shiro.spring.config.web.autoconfigure.ShiroWebAutoConfiguration, the bean id is shiroFilterChainDefinition, and it will be declared when there are no beans of the same type in the IOC container. And org.apache.shiro.spring.web.config.ShiroWebConfiguration also has a bean declaration with a bean id of shiroFilterChainDefinition, without any conditions, and both classes have @Configuration annotations, which means that when the classpath is at the same time When there are two classes, the configuration of shiroFilterChainDefinition in org.apache.shiro.spring.config.web.autoconfigure.ShiroWebAutoConfiguration does not take effect. I also cannot replace the default configuration by configuring shiroFilterChainDefinition myself. If I configure shiroFilterChainDefinition in my project it will appear [The bean 'shiroFilterChainDefinition', defined in class path resource [xxxx], could not be registered. A bean with that name has already been defined in class path resource [org / apache / shiro / spring / web / config / ShiroWebConfiguration.class] and overriding is disabled.] and the project fails to start. Can this be counted as a bug? Or is there any other solution?