Why IDEA Shows Errors for @Autowired Mapper Beans and How to Fix Them
This article explains why IntelliJ IDEA reports errors when injecting MyBatis @Mapper beans with @Autowired despite successful execution, and provides four practical solutions—including disabling inspections, adding Spring stereotypes, allowing null injection, and using @Resource—to eliminate the warnings.
Many developers encounter IDEA error messages when using @Autowired to inject a Mapper bean annotated with @Mapper, even though the program runs correctly.
The reason is that @Autowired expects a non‑null bean and IDEA can recognize Spring annotations but not MyBatis @Mapper, so it cannot verify the bean’s existence.
Solution 1: disable the inspection for autowiring in IDEA settings (Preferences → Editor → Inspections → Spring → Spring Core → Code → Autowiring for bean class) and change the severity from Error to Warning.
Solution 2: add a Spring stereotype annotation such as @Repository or @Component to the Mapper class.
Solution 3: allow the bean to be null by using @Autowired(required = false).
Solution 4: replace @Autowired with the standard @Resource annotation, which does not require a non‑null bean.
In summary, the IDEA warning occurs because @Autowired requires a non‑null bean and IDEA cannot detect the MyBatis @Mapper bean; using @Resource or one of the above fixes eliminates the warning.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Full-Stack Internet Architecture
Introducing full-stack Internet architecture technologies centered on Java
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.