NOTE
Spring AOP Source: Creating the Proxy
Advisor matching and creation of JDK-interface or class-based proxies around eligible Spring beans.
This is a historical learning note and may contain outdated or incomplete understanding.
For an eligible bean, Spring gathers candidate advisors/aspects, matches them against the target type/methods, and builds a proxy containing target metadata plus an interceptor/advisor chain.
Proxy strategy can use interface-based JDK proxies or class-based proxying depending on target/configuration. Final classes/methods and non-proxy call paths can constrain interception.
Treat specific proxy-factory class sequences as versioned internals; the stable model is match advisors → build interceptor chain → expose proxy.