You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2022. It is now read-only.
I am getting error when booting spring-social-showcase-boot in Eclipse. I am running as Java Application as spring boot allows.
Seems that it is not getting the spring social configuration, cause the error is:
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [org.springframework.social.facebook.api.Facebook] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}
The text was updated successfully, but these errors were encountered:
After doing this, it still failed because of a similar exception for LinkedIn and Twitter. Since I don't need those at the moment, I added a @Profile("linkedin") and @Profile("twitter") to the classes in org.springframework.social.showcase.linkedin and org.springframework.social.showcase.twitter. If starting without any profile, then Spring Boot will no longer complain that the controllers need that, since they are not started.
I guess that if you want linkedin or twitter, you need to add similar properties in application.properties with linkedin or twitter replacing facebook.
Hi @habuma , hope you are doing fine!!
I am getting error when booting spring-social-showcase-boot in Eclipse. I am running as Java Application as spring boot allows.
Seems that it is not getting the spring social configuration, cause the error is:
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [org.springframework.social.facebook.api.Facebook] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}
The text was updated successfully, but these errors were encountered: