This article dissects MyBatis startup internals, explaining how Mapper interfaces and XML SQL are parsed into MappedStatement objects, the role of SqlSource in static vs dynamic SQL, the #{}/${} difference, and how JDK dynamic proxies enable interface method execution without implementation classes.
The article provides a step‑by‑step analysis of Spring AOP’s proxy creation process, explaining why some beans are proxied, how @Order, @EnableAspectJAutoProxy, proxyTargetClass and exposeProxy affect proxying, the differences between JDK and CGLIB proxies, and why private, static or final methods cannot be intercepted.
MyBatis generates mapper implementations at runtime using JDK dynamic proxies; the proxy intercepts interface calls, builds a statementId from the interface’s fully‑qualified name and method name, looks up the corresponding MappedStatement via the namespace‑id convention, and delegates execution to SqlSession, eliminating the need for a concrete class.
This article explains the two proxy mechanisms used by Spring AOP—JDK dynamic proxy and CGLIB—detailing their core principles, required conditions, code examples, performance trade‑offs, how Spring chooses between them, common pitfalls that cause proxy failure, and practical solutions.
This article explains how Spring implements declarative transaction management using proxies, compares JDK dynamic proxies and CGLIB, demonstrates their behavior with code examples, and clarifies which method modifiers support transactional annotations in Spring applications.
This article provides a comprehensive analysis of Spring AOP's core proxy mechanisms, detailing the roles of advisor, advice, and pointcut classes, the annotation‑driven configuration process, and how Spring Boot automatically creates proxies using JDK or CGLIB based on configuration flags.
