SilenceLurker commented on issue #1236: URL: https://github.com/apache/shiro/issues/1236#issuecomment-2143453967
Good news and bad news: The good news is that by separating the implementation of ShiroFilterFactoryBean for FactoryBean and BeanPostProcessor, and injecting a shared instance of an additional entity class into both, we can eliminate these warnings without changing the original functionality. This approach requires resetting the test cases by configuring the original Map into the newly created entity class for storing corresponding information and injecting this entity into the FactoryBean (ShiroFilterFactoryBean) and the BeanPostProcessor implementations. This issue took me a considerable amount of time to resolve. However, the downside is that when users configure ShiroFilterFactoryBean, the Bean created in the Configuration will no longer be ShiroFilterFactoryBean but the newly created entity class (which will be automatically injected into the FactoryBean and BeanPostProcessor implementations via @Autowired). In my tests, this setup appears to function correctly without genera ting warnings (though I haven't conducted exhaustive testing because I am busy with my graduation project). Unfortunately, if users try to create a Bean of AuthorizationAttributeSourceAdvisor in the Configuration class, warnings still appear. I haven't found the cause of this issue yet. Does anyone have any ideas?(Translated by GPT4o) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
