kotlin-spring-proxy-compatibility

Your @Transactional annotation is likely ignored because Kotlin classes are final by default, preventing Spring from creating proxies. You need the all-open compiler plugin to allow Spring AOP interception and enable transactional behavior at runtime.

To fix Spring AOP proxy failures for annotations like @Cacheable and @Async, you must verify method visibility and ensure Kotlin compiler plugins are configured correctly so Spring can properly intercept and proxy your bean boundaries.

Yes, self-invocation bypasses Spring proxies because internal method calls do not route through the proxy instance. Analyzing bean boundaries and ensuring correct bean access is required to maintain transactional and caching behavior during execution.

The best way to debug Spring AOP proxy boundaries is to analyze bean access patterns, verify class openness through compiler plugins, and check method visibility to ensure correct runtime interception for transactional, caching, and security behavior.

Yes, you need the Kotlin all-open compiler plugin for Spring Boot transactional behavior because it opens classes for subclassing. Without it, Spring cannot apply AOP proxies to final classes, causing transaction interception to fail.