设计模式 2-模板模式与策略模式 (由Spring源码引发的思考-doGetBean方法)

引发思考的代码,究竟是模板模式还是策略模式那?

protected Object <pre name="code" class="java">doGetBean<span style="font-family: Arial, Helvetica, sans-serif;">(  final String name, final Class requiredType, final Object[] args, boolean typeCheckOnly) throws BeansException {  </span>

final String beanName = transformedBeanName(name); Object bean = null; Object sharedInstance = getSingleton(beanName); if (sharedInstance != null) { if (logger.isDebugEnabled()) { if (isSingletonCurrentlyInCreation(beanName)) { logger.debug("Returning eagerly cached instance of singleton bean '" + beanName + "' that is not fully initialized yet - a consequence of a circular reference"); } else { logger.debug("Returning cached instance of singleton bean '" + beanName + "'"); } } bean = getObjectForBeanInstance(sharedInstance, name, beanName, null); } else { if (isPrototypeCurrentlyInCreation(beanName)) { throw new BeanCurrentlyInCreationException(beanName); } BeanFactory parentBeanFactory = getParentBeanFactory(); if (parentBeanFactory != null && !containsBeanDefinition(beanName)) { String nameToLookup = originalBeanName(name); if (args != null) { return parentBeanFactory.getBean(nameToLookup, args); } else { return parentBeanFactory.getBean(nameToLookup, requiredType); } } if (!typeCheckOnly) { markBeanAsCreated(beanName); } final RootBeanDefinition mbd = getMergedLocalBeanDefinition(beanName); checkMergedBeanDefinition(mbd, beanName, args); String[] dependsOn = mbd.getDependsOn(); if (dependsOn != null) { for (int i = 0; i < dependsOn.length; i++) { String dependsOnBean = dependsOn[i]; getBean(dependsOnBean); registerDependentBean(dependsOnBean, beanName); } } if (mbd.isSingleton()) { sharedInstance = getSingleton(beanName, new ObjectFactory() { public Object getObject() throws BeansException { try { return createBean(beanName, mbd, args); } catch (BeansException ex) { destroySingleton(beanName); throw ex; } } }); bean = getObjectForBeanInstance(sharedInstance, name, beanName, mbd); } else if (mbd.isPrototype()) { Object prototypeInstance = null; try { beforePrototypeCreation(beanName); prototypeInstance = createBean(beanName, mbd, args); } finally { afterPrototypeCreation(beanName); } bean = getObjectForBeanInstance(prototypeInstance, name, beanName, mbd); } else { String scopeName = mbd.getScope(); final Scope scope = (Scope) this.scopes.get(scopeName); if (scope == null) { throw new IllegalStateException("No Scope registered for scope '" + scopeName + "'"); } try { Object scopedInstance = scope.get(beanName, new ObjectFactory() { //问题出现在这里 public Object getObject() throws BeansException { beforePrototypeCreation(beanName); try { return createBean(beanName, mbd, args);//还有这里 } finally { afterPrototypeCreation(beanName); } } }); bean = getObjectForBeanInstance(scopedInstance, name, beanName, mbd); } catch (IllegalStateException ex) { throw new BeanCreationException(beanName, "Scope '" + scopeName + "' is not active for the current thread; " + "consider defining a scoped proxy for this bean if you intend to refer to it from a singleton", ex); } } } if (requiredType != null && bean != null && !requiredType.isAssignableFrom(bean.getClass())) { throw new BeanNotOfRequiredTypeException(name, requiredType, bean.getClass()); } return bean; }

上面的代码是 Spring BeanFactory.getBean(String beanName)这个方法的,这是springIOC最基础的方法,但是在研读他的源码时有一段代码却让我很迷惑,代码如下:

 Object scopedInstance = scope.get(beanName, new ObjectFactory() { //问题出现在这里
                    public Object getObject() throws BeansException {        
                        beforePrototypeCreation(beanName);  
                        try {  
                            return createBean(beanName, mbd, args);//还有这里
                        }  
                        finally {  
                            afterPrototypeCreation(beanName);  
                        }  
                    }  
                });  
                bean = getObjectForBeanInstance(scopedInstance, name, beanName, mbd);  

上面的ObjectFactory是一个借口,里面定义了一个方法,这里使用匿名内部类实现了这个方法,按照我的理解,这应该是模板模式的回调方法,

下面的 createBean方法是这个类的一个抽象方法,这里调用了他,他的实现方法在子类中.

我不禁疑问,这两个模式的区别与不同在哪里那.

我专门查了书: