Framework: Warning message with Spring Boot 1.4.0.RELEASE

[vaadin-bot]

Originally by [email protected]_

---

Just upgraded to using Spring Boot 1.4 and started getting the following warning whenever running:

2016-07-30 16:15:16.505 WARN 10220 --- [ main] o.s.c.a.ConfigurationClassPostProcessor : Cannot enhance @Configuration bean definition 'com.vaadin.spring.VaadinConfiguration' 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'.

Not sure how much of an issue it is. It's discussed here:
https://jira.spring.io/browse/SPR-14234
and
https://github.com/spring-cloud/spring-cloud-config/issues/401

---

Imported from https://dev.vaadin.com/ issue #20099

[vaadin-bot]

Originally by _HermanBovens_

---

I'm having this issue as well.

[vaadin-bot]

Originally by _JoeKienzle_

---

Me as well. How do I solve this issue?

[HermanBovens]

This error probably also leads to another:
The Navigator used does not extend SpringNavigator. View scope support may be limited, and future versions of Vaadin Spring may remove support for using a plain Navigator.
This is because the VaadinConfiguration provides auto-configuration which includes @EnableVaadinNavigation which provides the SpringNavigator.

[remyvrs]

Hi guys,

Is there any follow up or workaround for this ?

BR

[dtitov]

UP?

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

[stale[bot]]

The issue was automatically closed due to inactivity. If you found some new details to it or started working on it, comment on the issue so that maintainers can re-open it.