基础Bean定义

public class TestAopBean implements InitializingBean, DisposableBean {

    @Override
    public void destroy() throws Exception {
        System.out.println("我被销毁了");
    }

    @Override
    public void afterPropertiesSet() throws Exception {
        System.out.println("我初始化完成了");
    }
}

定义增强BeanPostProcessor

public class TestAopBeanPostProcessor implements BeanPostProcessor  {

    @Override
    public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {
        if (bean.getClass() == TestAopBean.class) {
            ProxyFactory factory = new ProxyFactory();
            factory.setTarget(bean);
            factory.addAdvice(new TestAopBeanMethodInterceptor());
            Object proxy = factory.getProxy();
            return proxy;
        }
        return bean;
    }

    @Override
    public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {
        return bean;
    }

    private static class TestAopBeanMethodInterceptor implements MethodInterceptor {

        @Override
        public Object invoke(MethodInvocation invocation) throws Throwable {
            String methodName = invocation.getMethod().getName();
            System.out.println("我进来过，" + methodName);
            return invocation.proceed();
        }
    }
}

通过IDEA启动服务并关闭，控制台日志。可以看到，bean销毁时没有进入代理bean的代理方法

15:09:03.090 INFO  [main] c.c.d.s.test.web.Application[SpringApplication.java:655] -> The following profiles are active: dev
15:09:05.073 WARN  [main] c.n.c.s.URLConfigurationSource[URLConfigurationSource.java:121] -> No URLs will be polled as dynamic configuration sources.
我进来过，afterPropertiesSet
我初始化完成了
15:09:05.479 WARN  [main] c.n.c.s.URLConfigurationSource[URLConfigurationSource.java:121] -> No URLs will be polled as dynamic configuration sources.
15:09:06.285 WARN  [main] o.s.b.a.f.FreeMarkerAutoConfiguration[FreeMarkerAutoConfiguration.java:67] -> Cannot find template location(s): [classpath:/templates/] (please add some templates, check your FreeMarker configuration, or set spring.freemarker.checkTemplateLocation=false)
15:09:06.399 WARN  [main] o.s.c.l.c.BlockingLoadBalancerClientAutoConfiguration$BlockingLoadBalancerClientRibbonWarnLogger[BlockingLoadBalancerClientAutoConfiguration.java:86] -> You already have RibbonLoadBalancerClient on your classpath. It will be used by default. As Spring Cloud Ribbon is in maintenance mode. We recommend switching to BlockingLoadBalancerClient instead. In order to use it, set the value of `spring.cloud.loadbalancer.ribbon.enabled` to `false` or remove spring-cloud-starter-netflix-ribbon from your project.
15:09:08.015 WARN  [main] c.n.d.InstanceInfoReplicator[InstanceInfoReplicator.java:110] -> Ignoring onDemand update due to rate limiter
15:09:08.146 INFO  [main] c.c.d.s.test.web.Application[StartupInfoLogger.java:61] -> Started Application in 6.576 seconds (JVM running for 8.795)
Disconnected from the target VM, address: '127.0.0.1:64871', transport: 'socket'
15:09:27.375 WARN  [SpringContextShutdownHook] c.n.discovery.DiscoveryClient[DiscoveryClient.java:1335] -> Saw local status change event StatusChangeEvent [timestamp=1604560167375, current=DOWN, previous=UP]
15:09:27.378 WARN  [DiscoveryClient-InstanceInfoReplicator-0] c.n.discovery.DiscoveryClient[DiscoveryClient.java:1335] -> Saw local status change event StatusChangeEvent [timestamp=1604560167378, current=UP, previous=DOWN]
15:09:27.379 WARN  [DiscoveryClient-InstanceInfoReplicator-0] c.n.d.InstanceInfoReplicator[InstanceInfoReplicator.java:110] -> Ignoring onDemand update due to rate limiter
我被销毁了

Process finished with exit code 130 (interrupted by signal 2: SIGINT)

查看BeanPostProcessor的源码，关注：DestructionAwareBeanPostProcessor

 * @see DestructionAwareBeanPostProcessor
 * @see ConfigurableBeanFactory#addBeanPostProcessor
 * @see BeanFactoryPostProcessor
 */
public interface BeanPostProcessor {

DestructionAwareBeanPostProcessor定义，扩展了BeanPostProcessor接口，同时支持在bean销毁时执行自定义的回调

/**
 * Subinterface of {@link BeanPostProcessor} that adds a before-destruction callback.
 *
 * <p>The typical usage will be to invoke custom destruction callbacks on
 * specific bean types, matching corresponding initialization callbacks.
 *
 * @author Juergen Hoeller
 * @since 1.0.1
 */
public interface DestructionAwareBeanPostProcessor extends BeanPostProcessor {

综上，如果想通过BeanPostProcessor代理某个bean的destroy方法，可实现DestructionAwareBeanPostProcessor接口达到目标