【源码分析设计模式 9】SpringIOC中的模板方法模式，一招教你看懂Netty

package com.guor.template;

public abstract class SoyaMilk {

//模板方法, make , 模板方法可以做成final , 不让子类去覆盖.

final void make() {

select();

addCondiments();

soak();

beat();

}

//选材料

void select() {

System.out.println("第一步：选择好的新鲜黄豆 ");

}

//添加不同的配料， 抽象方法, 子类具体实现

abstract void addCondiments();

//浸泡

void soak() {

System.out.println("第三步， 黄豆和配料开始浸泡， 需要3小时 ");

}

void beat() {

System.out.println("第四步：黄豆和配料放到豆浆机去打碎 ");

}

}

2、花生类

---

package com.guor.template;

public class PeanutSoyaMilk extends SoyaMilk {

@Override

void addCondiments() {

System.out.println(" 加入上好的花生 ");

}

}

3、红豆类

---

package com.guor.template;

public class RedBeanSoyaMilk extends SoyaMilk {

@Override

void addCondiments() {

System.out.println(" 加入上好的红豆 ");

}

public static void main(String[] args) {

//制作红豆豆浆

System.out.println("----制作红豆豆浆----");

SoyaMilk redBeanSoyaMilk = new RedBeanSoyaMilk();

redBeanSoyaMilk.make();

System.out.println("----制作花生豆浆----");

SoyaMilk peanutSoyaMilk = new PeanutSoyaMilk();

peanutSoyaMilk.make();

}

}

4、控制台输出

---

七、SpringIOC中的模板方法模式

---

![](https://img-blog.csdnimg

《一线大厂Java面试题解析+后端开发学习笔记+最新架构讲解视频+实战项目源码讲义》

【docs.qq.com/doc/DSmxTbFJ1cmN1R2dB】 完整内容开源分享

.cn/20200611140842982.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2d1b3J1aV9qYXZh,size_16,color_FFFFFF,t_70)

Spring中几乎所有的扩展都是用了模板方法模式，以SpringIOC为例简单说明一下。

1、首先定义一个接口ConfigurableApplicationContext，声明模板方法refresh。

public interface ConfigurableApplicationContext extends ApplicationContext, Lifecycle, Closeable {

/*声明了一个模板方法/

void refresh() throws BeansException, IllegalStateException;

}

2、抽象类AbstractApplicationContext实现了接口

主要实现了模板方法refresh（这个方法很重要，是各种IOC容器初始化的入口）的逻辑。

/**

• 模板方法的具体实现

*/

public void refresh() throws BeansException, IllegalStateException {

synchronized (this.startupShutdownMonitor) {

// Prepare this context for refreshing.

prepareRefresh();

//注意这个方法是，里面调用了两个抽象方法refreshBeanFactory、getBeanFactory

// Tell the subclass to refresh the internal bean factory.

ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();

// Prepare the bean factory for use in this context.

prepareBeanFactory(beanFactory);

try {

//注意这个方法是钩子方法

// Allows post-processing of the bean factory in context subclasses.

postProcessBeanFactory(beanFactory);

// Invoke factory processors registered as beans in the context.

invokeBeanFactoryPostProcessors(beanFactory);

// Register bean processors that intercept bean creation.

registerBeanPostProcessors(beanFactory);

// Initialize message source for this context.

initMessageSource();

// Initialize event multicaster for this context.

initApplicationEventMulticaster();

//注意这个方法是钩子方法

// Initialize other special beans in specific context subclasses.

onRefresh();

// Check for listener beans and register them.

registerListeners();

// Instantiate all remaining (non-lazy-init) singletons.

finishBeanFactoryInitialization(beanFactory);

// Last step: publish corresponding event.

finishRefresh();

} catch (BeansException ex) {

// Destroy already created singletons to avoid dangling resources.

destroyBeans();

// Reset ‘active’ flag.

cancelRefresh(ex);

// Propagate exception to caller.

throw ex;

}

}

}

这里最主要有一个抽象方法obtainFreshBeanFactory、两个钩子方法postProcessBeanFactory和onRefresh，看看他们在类中的定义

两个钩子方法

protected void postProcessBeanFactory(ConfigurableListableBeanFactory beanFactory) {

}

protected void onRefresh() throws BeansException {

// For subclasses: do nothing by default.

}

再看看获取Spring容器的抽象方法：

/其实他内部只调用了两个抽象方法/

protected ConfigurableListableBeanFactory obtainFreshBeanFactory() {

refreshBeanFactory();

ConfigurableListableBeanFactory beanFactory = getBeanFactory();

if (logger.isDebugEnabled()) {

logger.debug("Bean factory for " + getDisplayName() + ": " + beanFactory);

}

return beanFactory;

}

protected abstract void refreshBeanFactory() throws BeansException, IllegalStateException;

public abstract ConfigurableListableBeanFactory getBeanFactory() throws IllegalStateException;

具体要取那种BeanFactory容器的决定权交给了子类！

3、AbstractRefreshableApplicationContext