New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BeanPostProcessorChecker] WARN o.s.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker #1236
Comments
Hi, Can you please follow what's in https://github.com/apache/shiro/tree/main/samples/spring-boot-3-web sample? |
run the sample/spring-boot-3-web,Warning still exists chang to spring boot 3.2.0
the pom is: |
use spring boot 3.1.5 also show the message info:
|
Thank you for your detailed explanation. There is something indeed new in how SpringBoot 3 initializes beans. Thank you! |
Found some prior discussions about this https://issues.apache.org/jira/browse/SHIRO-743 and spring-projects/spring-boot#16097 Looks like this is a long-standing issue, if any Spring experts want to take it on... please do! |
Thank you for your reply, shiro hava a Improvement, have plan to fix? |
No plan, we need help with this from the community. |
ok, thanks |
Reopened since this is a real issue |
@joshlong Would you know of someone who can help Shiro with this issue? |
It's based on this issue: |
Thanks @rasa-app I have tried to create a PR, but still I cannot get rid of the warnings unfortunately. |
Not stale |
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. If you want to reproduce it, you might check out the demo I originally wrote:https://github.com/SilenceLurker/shiro-test |
Shiro team needs help on this. None of us are Spring experts that can deduce what's going on here. |
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 testing, so I think many others might have this issue but don't pay much attention to it. That demo might provide some ideas or something else to others, so let's just leave it there. |
Thank you! We appreciate any help we get here. |
@SilenceLurker Shiro no longer uses JIRA for issue tracking so you don’t need to create the JIRA account |
Search before asking
Question
my pom:
4.0.0
The text was updated successfully, but these errors were encountered: