Why IntelliJ IDEA Warns on @Autowired but Not on @Resource: Understanding Spring Field Injection

When developing with IntelliJ IDEA, you may notice a warning on fields annotated with Spring's @Autowired, stating that field injection is not recommended, while using @Resource does not trigger this warning.

Spring supports three common dependency injection (DI) methods: constructor injection (using constructor parameters), setter injection (calling setter methods), and field injection (annotating fields with @Autowired or @Resource).

The annotations differ: @Autowired is defined by Spring and defaults to by-type injection (with @Qualifier for name), applicable to constructors, methods, parameters, and fields; @Resource is defined by JSR‑250, defaults to by-name (falling back to by-type), and can be used on methods and fields only.

According to the Spring documentation, constructor injection is preferred for mandatory, immutable dependencies; setter injection suits optional or mutable dependencies; field injection should be minimized, and if used, @Resource offers slightly lower coupling to the IoC container than @Autowired.

Field injection has several drawbacks: it cannot enforce immutability, hides dependencies from external visibility, tightly couples components to the IoC container (making reuse and unit testing harder), and can obscure an excessive number of dependencies, indicating a possible violation of the single‑responsibility principle.

IDEA only warns on @Autowired because it is a Spring‑specific annotation, creating a strong binding between the code and the Spring framework; @Resource, being a Java standard (JSR‑250), is expected to be supported by any compliant IoC container, so the IDE does not flag it.

Note: The author includes a brief advertisement for a licensed IDEA subscription and encourages readers to like and share the post.