使用MyBatis时无法调用userMapper.kt接口及lateinit未初始化幽灵bug求助

Hey there, ghost bugs that pop up out of nowhere are the absolute worst—especially when everything worked perfectly just yesterday! Let’s walk through your two issues and break down likely fixes to get you back on track.

1. Can’t Call userMapper.kt Interface in servicePackage #

Here are the most common culprits and actionable fixes:

• Check MyBatis Mapper Scanning Configuration
  Make sure your app is correctly picking up mapper interfaces. If you’re using Spring Boot:
  • Add @MapperScan("com.yourproject.path.to.mappers") to your main application class (swap the package path for where your userMapper.kt lives).
  • Alternatively, annotate userMapper.kt directly with @Mapper to explicitly mark it as a MyBatis mapper.
• Verify Dependency Injection Setup
  In your service class, ensure you’re properly injecting the mapper. Avoid relying solely on lateinit without injection annotations:

  @Service
  class UserService {
      @Autowired // Or use constructor injection (preferred for Kotlin)
      private lateinit var userMapper: UserMapper
      // ... your service logic
  }
  

  Constructor injection is more reliable and avoids lateinit pitfalls entirely:

  @Service
  class UserService(private val userMapper: UserMapper) {
      // ... your service logic
  }
  

• Check Kotlin Visibility Modifiers
  Double-check that userMapper.kt is a public interface (Kotlin defaults to public, but it’s easy to accidentally mark it as internal, which blocks access outside its module or package).

2. lateinit Object Still Not Initialized #

Remember: lateinit only tells the compiler you’ll initialize the variable later—it doesn’t handle initialization itself. Here’s why this might be happening:

• Failed Dependency Injection
  This is almost always linked to the first issue. If userMapper isn’t being scanned or injected correctly, the lateinit variable in your service will never get initialized. Fixing the mapper scanning/injection from the first section will likely resolve this.
• Component Scanning Gaps
  Confirm your servicePackage is being scanned by Spring. If your main app class is in a different root package, update @SpringBootApplication to include your service package:

  @SpringBootApplication(scanBasePackages = ["com.yourproject.servicePackage", "com.yourproject.mappers"])
  class YourApplication
  

• Build/Cache Corruption
  Since this worked yesterday, corrupted build cache is a prime suspect. Try:
  • Running a clean build: For Gradle, use ./gradlew clean build; for Maven, mvn clean install.
  • Restarting your IDE and invalidating caches (most IDEs have an "Invalidate Caches / Restart" option in the File menu—this fixes weird IDE indexing issues all the time).
• Accidental Dependency Version Changes
  Double-check your build files (build.gradle.kts or pom.xml) to ensure you didn’t accidentally update MyBatis, Spring Boot, or related dependencies—version mismatches can break injection overnight without warning.

Quick Debugging Tips #

• Enable DEBUG logging for Spring and MyBatis. Look for logs about bean creation, mapper scanning, or injection failures—this will point you directly to the root cause.
• Verify your application’s config files (application.yml or application.properties) haven’t been modified accidentally—incorrect database or MyBatis settings can prevent mapper initialization.

内容的提问来源于stack exchange，提问作者colinstark