I have created a simple unit test but IntelliJ is incorrectly highlighting it red. marking it as an error
No beans?
https://i.stack.imgur.com/4cCFH.png
As you can see below it passes the test? So it must be Autowired?
https://i.stack.imgur.com/YFGln.png
I had this same issue when creating a Spring Boot application using their @SpringBootApplication
annotation. This annotation represents @Configuration
, @EnableAutoConfiguration
and @ComponentScan
according to the spring reference.
As expected, the new annotation worked properly and my application ran smoothly but, Intellij kept complaining about unfulfilled @Autowire
dependencies. As soon as I changed back to using @Configuration
, @EnableAutoConfiguration
and @ComponentScan
separately, the errors ceased. It seems Intellij 14.0.3 (and most likely, earlier versions too) is not yet configured to recognise the @SpringBootApplication
annotation.
For now, if the errors disturb you that much, then revert back to those three separate annotations. Otherwise, ignore Intellij...your dependency resolution is correctly configured, since your test passes.
Always remember...
Man is always greater than machine.
Add Spring annotation @Repository
over the repository class.
I know it should work without this annotation. But if you add this, IntelliJ will not show error.
@Repository
public interface YourRepository ...
...
If you use Spring Data with extending Repository
class it will be conflict packages. Then you must indicate packages directly.
import org.springframework.data.repository.Repository;
...
@org.springframework.stereotype.Repository
public interface YourRepository extends Repository<YourClass, Long> {
...
}
And next you can autowired your repository without errors.
@Autowired
YourRepository yourRepository;
It probably is not a good solution (I guess you are trying to register repository twice). But work for me and don't show errors.
Maybe in the new version of IntelliJ can be fixed: https://youtrack.jetbrains.com/issue/IDEA-137023
My version of IntelliJ IDEA Ultimate (2016.3.4 Build 163) seems to support this. The trick is that you need to have enabled the Spring Data plugin.
https://i.stack.imgur.com/pIdbk.png
Sometimes you are required to indicate where @ComponentScan should scan for components. You can do so by passing the packages as parameter of this annotation, e.g:
@ComponentScan(basePackages={"path.to.my.components","path.to.my.othercomponents"})
However, as already mentioned, @SpringBootApplication annotation replaces @ComponentScan, hence in such cases you must do the same:
@SpringBootApplication(scanBasePackages={"path.to.my.components","path.to.my.othercomponents"})
At least in my case, Intellij stopped complaining.
@SpringBootApplication(scanBasePackages={"com.a.b, com.a.c"})
and although the app worked fine, intellij didn't like it. Changing to @SpringBootApplication(scanBasePackages={"com.a.b", "com.a.c"})
fixed for me!
I always solve this problem doing de following.. Settings>Inspections>Spring Core>Code than you shift from error to warning the severity option
https://i.stack.imgur.com/9c4Xw.jpg
Incorrect injection point autowiring in Spring bean components
.
I am using spring-boot 2.0, and intellij 2018.1.1 ultimate edition and I faced the same issue.
I solved by placing @EnableAutoConfiguration in the main application class
@SpringBootApplication
@EnableAutoConfiguration
class App{
/**/
}
Redundant declaration: @SpringBootApplication already applies @EnableAutoConfiguration
¯\_(ツ)_/¯
@EnableAutoConfiguration
Check if you missed @Service annotation in your service class, that was the case for me.
Putting @Component
or @configuration
in your bean config file seems to work, ie something like:
@Configuration
public class MyApplicationContext {
@Bean
public DirectoryScanner scanner() {
return new WatchServiceDirectoryScanner("/tmp/myDir");
}
}
@Component
public class MyApplicationContext {
@Bean
public DirectoryScanner scanner() {
return new WatchServiceDirectoryScanner("/tmp/myDir");
}
}
Configure application context and all will be ok.
https://i.stack.imgur.com/gg3BF.png
Have you checked that you have used @Service
annotation on top of your service implementation? It worked for me.
import org.springframework.stereotype.Service;
@Service
public class UserServiceImpl implements UserServices {}
Use @EnableAutoConfiguration
annotation with @Component
at class level. It will resolve this problem.
For example:
@Component
@EnableAutoConfiguration
public class ItemDataInitializer {
@Autowired
private ItemReactiveRepository itemReactiveRepository;
@Autowired
private MongoOperations mongoOperations;
}
If you don't want to make any change to you code just to make your IDE happy. I have solved it by adding all components to the Spring facet.
Create a group with name "Service, Processors and Routers" or any name you like; Remove and recreate "Spring Application Context" use the group you created previously as a parent.
https://i.stack.imgur.com/NLiWU.png
For me the solution was to place @EnableAutoConfiguration
in the Application class under the @SpringBootApplication
its going to underline it because its redundant. Delete it and voila all you warnings regarding missing beans are vanished! Silly Spring...
And one last piece of important information - add the ComponentScan
so that the app knows about the things it needs to wire. This is not relevant in the case of this question. However if no @autowiring
is being performed at all then this is likely your solution.
@Configuration
@ComponentScan(basePackages = {
"some_package",
})
public class someService {
As long as your tests are passing you are good, hit alt + enter
by taking the cursor over the error and inside the submenu of the first item you will find Disable Inspection
select that
simple you have to do 2 steps
add hibernate-core dependency change @Autowired to @Resource.
==>> change @Autowired to @Resource
I am using this annotation to hide this error when it appears in IntelliJ v.14:
@SuppressWarnings("SpringJavaAutowiringInspection")
@SuppressWarnings("SpringJavaInjectionPointsAutowiringInspection")
I had similar issue in Spring Boot application. The application utilizes Feign (HTTP client synthetizing requests from annotated interfaces). Having interface SomeClient
annotated with @FeignClient
, Feign generates runtime proxy class implementing this interface. When some Spring component tries to autowire bean of type SomeClient
, Idea complains no bean of type SomeClient
found since no real class actually exists in project and Idea is not taught to understand @FeignClient
annotation in any way.
Solution: annotate interface SomeClient
with @Component
. (In our case, we don't use @FeignClient
annotation on SomeClient
directly, we rather use metaannotation @OurProjectFeignClient
which is annotated @FeignClient
and adding @Component
annotation to it works as well.)
@Component
to the interface solves the issue. But I think this is not the correct way... In my opinion this is a bug in IntelliJ IDEA or to be not so hard IntelliJ IDEA is not ready for newer Feign versions. It works without @Component
in erlier feign versions (where the @FeignClient
annotation was in org.springframework.cloud.netflix.feign
instead of org.springframework.cloud.openfeign
- maybe this is the cause of the issue?). Have you found any further details (maybe a bug ticket) for this?
@Component
) is @FeignClient
from org.springframework.cloud.netflix.feign
) package.
As most synchronisation errors between IntelliJ (IDE) and development environments.
Specially if you have automated tests or build that pass green all the way through.
Invalidate Cache and Restart solved my problem.
What you need to do is add
@ComponentScan("package/include/your/annotation/component")
in AppConfiguration.java
.
Since I think your AppConfiguraion.java
's package is deeper than your annotation component (@Service, @Component...)'s package,
such as "package/include/your/annotation/component/deeper/config"
.
I had a similar problem in my application. When I added annotations incorrect highliting dissapeared.
@ContextConfiguration(classes = {...})
in my Case, the Directory I was trying to @Autowired was not at the same level,
after setting it up at the same structure level, the error disappeared
hope it can helps some one!
IntelliJ IDEA Ultimate
Add your main class to IntelliJ Spring Application Context, for example Application.java
File
-> Project Structure..
left side: Project Setting -> Modules
right side: find in your package structure Spring
and add +
Application.java
just add below two annotations to your POJO.
@ComponentScan
@Configuration
public class YourClass {
//TODO
}
My solution to this issue in my spring boot application was to open the spring application context and adding the class for the missing autowired bean manually!
(access via Project Structure menu or spring tool window... edit "Spring Application Context")
So instead of SpringApplicationContext just containing my ExampleApplication spring configuration it also contains the missing Bean:
SpringApplicationContext:
ExampleApplication.java
MissingBeanClass.java
et voilà: The error message disappeared!
This seems to still be a bug in the latest IntelliJ and has to do with a possible caching issue?
If you add the @Repository annotation as mk321 mentioned above, save, then remove the annotation and save again, this fixes the problem.
Sometimes - in my case that is - the reason is a wrong import. I accidentally imported
import org.jvnet.hk2.annotations.Service
instead of
import org.springframework.stereotype.Service
by blindly accepting the first choice in Idea's suggested imports. Took me a few minutes the first time it happend :-)
All you need to do to make this work is the following code:
@ComponentScan
public class PriceWatchTest{
@Autowired
private PriceWatchJpaRepository priceWatchJpaRepository;
...
...
}
I just had to use @EnableAutoConfiguration to address it, however this error had no functional impact.
It can be solved by placing @EnableAutoConfiguration on spring boot application main class.
Success story sharing
@SpringBootApplication
I was receiving this error. I followed the advice of @Jaõs Matos by using thescanBasePackages
parameter to@SpringBootApplication
and specified the package/namespaces that should be scanned.