kotlin-spring-proxy-compatibility

Spring proxy interception fails in Kotlin when classes are final by default or required Kotlin Spring compiler plugins are missing. This Skill diagnoses these proxy failures and recommends enabling the correct plugins and restructuring beans to ensure annotated methods are intercepted.

Fix Spring AOP self-invocation in Kotlin by restructuring bean boundaries so annotated methods are called through a proxied reference rather than internally. This Skill diagnoses self-invocation call paths and proposes safe restructuring to ensure proxy interception functions correctly.

Yes, the Kotlin Spring compiler plugin is required to open Kotlin classes and allow Spring to create proxies for AOP interception. This Skill checks your plugin configurations and identifies when missing compiler plugins cause cacheable, async, or security annotations to fail.

Spring cacheable and async annotations do nothing in Kotlin when proxy interception fails due to final classes, missing compiler plugins, or interface versus class proxy mismatches. This Skill performs scoped checks on beans and configurations to identify the failure scenario and recommend fixes.

Kotlin final-by-default semantics break Spring proxy behavior by preventing subclass-based proxies from overriding annotated methods for interception. This Skill identifies when final classes block AOP interception and recommends enabling Kotlin Spring compiler plugins to open classes for proxying.

Choose interface proxies when your Kotlin beans implement interfaces, and class proxies when they do not, as mismatched proxy types cause interception failures. This Skill checks your proxy type configuration against your bean structure to ensure correct AOP interception.