-
Notifications
You must be signed in to change notification settings - Fork 508
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
Cannot enhance @Configuration bean definition 'beanNamePlaceholderRegistryPostProcessor' #29
Comments
As far as I can see in the code, it has been already declared as static return, why does it still complain? |
FYI:
By adding the
which I did not do before. |
do you need further help? |
For the tomcat one, yes. |
I still have the tomcat issue, but the FYI message is just for another issue. |
no way to reopen this? |
Yeah, please reopen and explain what's the situation. If you have sample code where the issue manifests even better so I can test and make sure I got you covered. |
I found there is no way to re-open the issue. The jar actually works pretty well with my sample codebase, but the real integration does the opposite. |
As far as warnings go,beanNamePlaceholderRegistryPostProcessor has been static for a while and there's no warning being raised. Check out the demo apps, there's a bunch of them |
what's the "real" integration? Can you create a repo with a "real" example in your github accound and share it with me? |
Yes, I was trying to confirm with you whether you have seen that issue first. Now, I guess I need to try to reproduce the issue now. I still do not know the root cause yet. |
Will get back to this by the end of this week. |
Seeing this issue with "com.github.ulisesbocchio:jasypt-spring-boot-starter:1.8" |
@gorky, Can you explain what you see? Is it just the warning? On tomcat? Do you have a code sample? |
Thanks for your quick reply! It's the Tomcat that is embedded in Spring Boot, although it hasn't started when these methods are logged. I don't currently have a code sample I can post in a public forum (my apologies). We are using org.springframework.boot.loader.PropertiesLauncher with -Dloader.path set to include the jars that have our jasypt beans defined. Feel free to PM me. Regards, |
Found the issue with the jar not being picked up -- a directory name had be changed w/o an update in the -Dloader.path. When I corrected the directory name I started getting quite a few interesting failures -- trying to work my way through them. I will keep this thread updated. |
Alright, thanks, let me know if you need further assistance. I was checking the sample apps I have and I don't see the warning in any of them |
Ok, this is issue is resolved. I've walked into some others, but I can open a ticket and supply a test case. Feel free to close this one as "End User Configuration Error -- corrected". And thanks! |
The issue is fixed now in version 4.2.6, 4.3 RC2. Please refer this ticket https://jira.spring.io/browse/SPR-14234 |
I have tried to apply the similar setup for the other app, but I have encountered this issue.
Jun 27, 2016 12:33:50 PM org.apache.catalina.startup.VersionLoggerListener log WARNING: Cannot enhance @Configuration bean definition 'beanNamePlaceholderRegistryPostProcessor' since its singleton instance has been created too early. The typical cause is a non-static @Bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'.
Jun 27, 2016 12:34:25 PM org.apache.catalina.startup.TldConfig execute SEVERE: Context [] startup failed due to previous errors
Jun 27, 2016 12:34:32 PM org.springframework.web.context.support.XmlWebApplicationContext doClose
Can anyone takes a look at this?
The text was updated successfully, but these errors were encountered: