kotlin-spring-proxy-compatibility

Kotlin Spring @Transactional interception often fails due to final-by-default classes, missing kotlin-spring compiler plugins, or self-invocation bypassing proxy boundaries. Diagnosing proxy strategy and class visibility identifies the root cause for a safe production fix.

Fixing Kotlin Spring AOP interception requires verifying the kotlin-spring plugin is active, opening classes or using interface proxies, and eliminating internal self-invocation to ensure annotations like @Cacheable and @Async cross proxy boundaries correctly.

Kotlin final-by-default behavior prevents Spring from creating CGLIB class proxies, silently breaking AOP. Applying the kotlin-spring plugin opens classes for interception, restoring expected proxy behavior for transactional and caching annotations.

Diagnosing Spring AOP self-invocation in Kotlin involves tracing method calls to verify if they cross proxy boundaries. Internal calls bypass interception, so analyzing call flows and proxy strategy exposes where transactional or cache behavior is lost.

Choose interface proxies for Kotlin Spring when bean interfaces exist to avoid final class limitations, but class proxies are needed when intercepting concrete classes. Validating the configured proxy strategy ensures consistent AOP behavior across your project.