Understanding Static and Dynamic Proxy Patterns in Java
The proxy pattern is a foundational concept for understanding the underlying mechanics of Spring AOP. It allows you to control access to an object by providing a surrogate or placeholder.
Static Proxy
In a static proxy implementation, the proxy class is created manually or by specific tools before compilation.
Core Components:
Subject Interfac ...
Posted on Tue, 21 Jul 2026 16:09:44 +0000 by dan1956
How Annotations Work, How to Understand Their Implementation, and a Typical Annotation-driven AOP Workflow
1. The Core Principle of Annotations: "Marker + Parser" Duo
Compare an annotation to a label on a package:
Annotation = label (e.g., "Fragile", "Keep Refrigerated"). It only describes a property; it performs no action.
Parser = courier / warehouse worker. When they see the label, they perform the corresponding act ...
Posted on Sun, 19 Jul 2026 16:22:03 +0000 by quickphp
Implementing Aspect-Oriented Programming and Transaction Management in Spring
Core AOP Terminology
Aspect-Oriented Programming (AOP) in Spring relies on a specific set of concepts to modularize cross-cutting concerns. Understanding these terms is essential for configuring proxies and interceptors correctly:
Target Object: The original bean that contains the primary business logic.
Proxy: A dynamically generated wrapper ...
Posted on Sun, 21 Jun 2026 18:05:32 +0000 by ambrennan
Spring AOP Fundamentals and Implementation Techniques
Core Terminology
Target: Object being enhanced
Joinpoint: Method eligible for interception
Pointcut: Method actually intercepted
Advice
Weaving: Process of applying advice to target
Proxy: Enhanced object created after weaving
Aspect: Combination of pointcut and advice
Implementation Mechanisms
JDK Dynamic Proxy (for interface implementation ...
Posted on Mon, 25 May 2026 16:42:02 +0000 by mr.echo
Applying Advisors and Auto-Proxy Mechanisms for Method-Level AOP in Spring
When building AOP solutions with Spring's ProxyFactoryBean, a few practical limitations quickly surface: each proxy is tied to a single target bean, requiring multiple proxy definitions in large applications; the proxy's own ID must be used when retrieving the bean from the container, rather than the original target bean ID; and advice is appli ...
Posted on Sat, 09 May 2026 23:23:19 +0000 by briant