kotlin-spring-proxy-compatibility

Spring AOP proxy interception fails in Kotlin when classes are final-by-default, the Kotlin compiler plugin is missing, or methods are self-invoked. This Skill diagnoses proxy eligibility and boundary crossing to propose a minimal verifiable fix.

To fix Spring AOP proxy issues for @Cacheable and @Async in Kotlin, you must verify proxy eligibility, ensure method calls cross the proxy boundary, and apply correct compiler plugin configurations to restore annotation interception.

Yes, Kotlin final-by-default prevents Spring from creating AOP proxies for method interception. You need the proper Kotlin compiler plugin configurations to open classes and allow proxying for annotations like @Transactional.

Diagnosing self-invocation preventing Spring proxy interception in Kotlin involves verifying whether a method call crosses the proxy boundary. This Skill checks annotated methods to confirm if proxy interception is actually occurring at runtime.

The best way to configure Kotlin compiler plugins for Spring AOP is to verify existing plugin setups and proxy strategies. This ensures annotations like @Transactional and @Cacheable are properly intercepted by restoring proxy eligibility.

You need to check proxy eligibility for Spring annotations in Kotlin when runtime inconsistencies occur with @Transactional, @Cacheable, or @Async. This happens due to Kotlin final defaults, missing plugins, or self-invocation preventing proxying.