Why IntelliJ Flags @Autowired but Not @Resource: Understanding Spring DI Differences

Common Spring DI methods

Constructor injection : inject dependencies via constructor parameters.

Setter injection : inject dependencies by calling a setter method.

Field injection : inject dependencies directly on fields using @Autowired or @Resource.

@Autowired VS @Resource

Both annotations achieve dependency injection, but @Autowired is defined by Spring while @Resource follows the JSR‑250 specification. Their core functionality is similar, yet they differ in several details:

Dependency resolution : @Autowired defaults to byType and can use @Qualifier for name‑based injection; @Resource defaults to byName and falls back to byType if no matching name is found.

Applicable targets : @Autowired can be placed on constructors, methods, parameters, and fields; @Resource works only on methods and fields.

Provider : @Autowired is supplied by Spring , whereas @Resource is supplied by the JSR‑250 standard.

Advantages and disadvantages of each DI style

Constructor injection : enforces strong dependencies and immutability, ideal when dependencies are required and rarely change.

Setter injection : optional and mutable, suitable for dependencies that may be absent or change over time.

Field injection : very convenient but should be used sparingly; when necessary, @Resource couples less tightly to the IoC container than @Autowired.

Drawbacks of field injection

Cannot inject immutable objects as cleanly as constructor injection.

Dependencies are hidden from external view, making the class harder to understand.

Creates tight coupling between the component and the IoC container, complicating reuse outside the container.

Unit tests must also involve the IoC container.

When many dependencies are present, the constructor becomes unwieldy, indicating a possible violation of the Single Responsibility Principle.

Why IntelliJ only warns on @Autowired

Field injection is popular because it is extremely convenient; it avoids boilerplate code required by constructor or setter injection. However, @Autowired is a Spring‑specific annotation, tightly binding the code to the Spring framework. If the underlying IoC container changes, the annotation may no longer be supported. In contrast, @Resource is part of the Java standard (JSR‑250), so any compliant IoC container should handle it, offering better portability.

Why does IntelliJ show a warning for @Autowired but ignore @Resource ?

In short, the warning stems from IntelliJ’s awareness of Spring‑specific semantics; it flags the discouraged practice of field injection with a Spring‑specific annotation while treating the standard @Resource as acceptable.