Memory growth when repeatedly loading ApplicationContext with @Transactional beans lacking interfaces
Goal: determine whether the default CGLIB proxy created for @Transactional methods on beans without interfaces causes observable memory growth when ApplicationContext instances are repeatedly instantiated in a test loop without being closed. Uncertainty: Spring documentation notes that the proxy-target-class attribute can force JDK dynamic proxies, but the d
spring