SilenceLurker

I recently attempted to integrate Shiro in Spring-Boot 3.2.5 and it seemed to run normally at the time so I didn't pay much attention, but I noticed these warnings too....

I will spend some time trying to resolve this, but I cannot guarantee a solution. These warnings don't seem to have caused any project failures or functional abnormalities during my...

Got it, and, based on my recent attempts, I suspect that the issue might be related to Spring-Boot3 using the Spring6 framework, whereas Spring-Boot2 uses the Spring5 framework. It seems...

It seems that I initially found a tutorial that wasn't very good, which involved manually removing javax related dependencies one by one when importing dependencies. I will look further to...

I am not sure if this is the issue, but I noticed that ShiroFilterFactoryBean implements both FactoryBean and BeanPostProcessor interfaces. This could be the cause. However, I have not tried...

I have already started trying to do this, but it seems to be more complex than I initially thought. I might need two to three days, or even longer, to...

I haven't successfully completely separated them yet. I'm stuck on some tests, but I wrote another example to try it out and confirmed that the issue is indeed caused by...

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...

It seems that the implementation class of BeanPostProcessor should not be instantiated as a bean in a Configuration class. If the BeanPostProcessor is annotated with Component and handled automatically by...

Based on the content above, it may not be necessary to separate the original implementations. Instead, simply modifying them to be managed via the Component annotation might suffice. However, additional...