SpringIOC是Spring的一个核心功能：依赖注入或者控制反转。即创建对象来Spring Ioc容器来负责。换句话说，当我们需要一个对象时，不是由自己来创建，然后从SpringIOC容器中获取。那么在SpringIOC中自然已经持有了这个对象的所有信息，当需要创建的时候，就可以创建出此对象。
BeanDefinition 是POJO对象在spring内部数据结构的抽象。
BeanDefinition的内部，当然可以在Spring中得到，无非是一些变量和接口的定义。我们稍微介绍一下:
第一个singleton 和Prototype。这是两个属性，属于互斥的两个属性。Spring中定义对象有单例和非单例两种，我们可以在配置文件声明，这个属性自然也在BeanDefinition中定义。我们解释的问题就是为什么用这两个单词singleton和Prototype，或者说为什么用prototype表示非单例。 单例用singleton表示我们没有疑问。在设计模式中有单例Singleton和原型prototype模式。这两种都是创建型模式，其实这两个模式是互斥的。单例模式是创建一个对象，原型是用来创建多个对象。原型模式的实现原理是在内存中直接copy一个对象，即clone。这个会绕过对象的构造方法，所以私有化构造方法是没有任何效果的。
SpringIOC容器的启动分为三部：源的定位，资源的装载，以及资源的注册，核心方法refresh()。
一、BeanDefinition 资源定位
定位很简单，就是告诉Spring一个文件的路径和文件类型。比如：FileSystemXmlApplicationContext 、ClassPathXmlApplicatioContext、XmlWebApplication这三种文件类型相同，但是路径不同。我们以FileSystemXmlApplicationContext 分析下Spring的定位。这一节重要的内容其实是Spring的设计。
下面会涉及到多个类，尤其父子类之间的调用，子类调用父类中共有的实现，父类的调用抽象方法，具体实现放在子类中。
FileSystemXmlApplicationContext 孙子类
AbstractXmlApplicationContext 子类
AbstractRefreshableConfigApplicationContext 父类
AbstractRefreshableApplicationContext 祖类
AbstractApplicationContext 祖宗类**
这些是从上到下一路继承下来。
入口在FileSystemXmlApplicationContext 的一个构造方法中：
public FileSystemXmlApplicationContext(String[] configLocations, boolean refresh, ApplicationContext parent)
throws BeansException {
super(parent);
setConfigLocations(configLocations);
if (refresh) {
refresh();
}
}启动方法就是refresh()，上面还有一个setConfigLocations，下面的实现逻辑过程中，会用这个这个方法，我们在具体分析。这个方法就是设置文件，refresh是没有设置文件的，所以发现文件的设置和SpringIOC的启动过程是完全分离的。
这个refresh的定义是在祖父类中:AbstractApplicationContext,显然这个方法属于所有Spring共有的，定义在祖类中。
看下refresh的实现：
@Override
public void refresh() throws BeansException, IllegalStateException {
synchronized (this.startupShutdownMonitor) {
// Prepare this context for refreshing.
prepareRefresh();
// 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) {
logger.warn("Exception encountered during context initialization - cancelling refresh attempt", ex);
// Destroy already created singletons to avoid dangling resources.
destroyBeans();
// Reset 'active' flag.
cancelRefresh(ex);
// Propagate exception to caller.
throw ex;
}
}
}我们看这段代码:ConfigurableListableBeanFactory beanFactory = obtainFreshBeanFactory();
获得Beanfactory对象。
protected ConfigurableListableBeanFactory obtainFreshBeanFactory() {
a refreshBeanFactory();
b ConfigurableListableBeanFactory beanFactory = getBeanFactory();
if (logger.isDebugEnabled()) {
logger.debug("Bean factory for " + getDisplayName() + ": " + beanFactory);
}
return beanFactory;
}继续看这一行代码：refreshBeanFactory 在
AbstractRefreshableApplicationContext 祖类（刚才那个类的子类）
@Override
protected final void refreshBeanFactory() throws BeansException {
if (hasBeanFactory()) {
destroyBeans();
closeBeanFactory();
}
try {
DefaultListableBeanFactory beanFactory = createBeanFactory();
beanFactory.setSerializationId(getId());
customizeBeanFactory(beanFactory);
loadBeanDefinitions(beanFactory);
synchronized (this.beanFactoryMonitor) {
this.beanFactory = beanFactory;
}
}
catch (IOException ex) {
throw new ApplicationContextException("I/O error parsing bean definition source for " + getDisplayName(), ex);
}
}继续：
protected DefaultListableBeanFactory createBeanFactory() {
return new DefaultListableBeanFactory(getInternalParentBeanFactory());
}得到一个小结论：使用BeanFactory是:DefaultListableBeanFactory
我们这一节是研究BeanDefinition的定位，我们回到主题。
看下先这个过程，略微有点复杂
上面创建完Beanfactory，还有一个这个方法：
loadBeanDefinitions(beanFactory);
这个实现是在“子类”（这个已经到第四层了）：
AbstractXmlApplicationContext
@Override
protected void loadBeanDefinitions(DefaultListableBeanFactory beanFactory) throws BeansException, IOException {
// Create a new XmlBeanDefinitionReader for the given BeanFactory.
XmlBeanDefinitionReader beanDefinitionReader = new XmlBeanDefinitionReader(beanFactory);
// Configure the bean definition reader with this context's
// resource loading environment.
beanDefinitionReader.setEnvironment(this.getEnvironment());
beanDefinitionReader.setResourceLoader(this);
beanDefinitionReader.setEntityResolver(new ResourceEntityResolver(this));
// Allow a subclass to provide custom initialization of the reader,
// then proceed with actually loading the bean definitions.
initBeanDefinitionReader(beanDefinitionReader);
loadBeanDefinitions(beanDefinitionReader);
}
loadBeanDefinition使用XmlBeanDefinitionReader 完成的。
继续看 loadBeanDefinitions(beanDefinitionReader);
protected void loadBeanDefinitions(XmlBeanDefinitionReader reader) throws BeansException, IOException {
Resource[] configResources = getConfigResources();
if (configResources != null) {
reader.loadBeanDefinitions(configResources);
}
String[] configLocations = getConfigLocations();
if (configLocations != null) {
reader.loadBeanDefinitions(configLocations);
}}一个是getConfigResources 一个是getConfigLoactions 那么会调用那一个呢，
getConfigResources 是在ClassPathXmlWebapplictionContext定义的，在孙子类FileSystemXmlApplicationContext没有实现，他会调用子类AbstractXmlApplicationContext的实现
protected Resource[] getConfigResources() {
return null;
}
返回null。
getConfigLoactions 的实现在 父类（第三层）
AbstractRefreshableConfigApplicationContext
protected String[] getConfigLocations() {
return (this.configLocations != null ? this.configLocations : getDefaultConfigLocations());
}我们此时看下这个会不会返回null。
我们此前提供在refresh调用之前有一个 setConfigLocations(configLocations);方法
我们看下这个的实现:
public void setConfigLocations(String... locations) {
if (locations != null) {
Assert.noNullElements(locations, "Config locations must not be null");
this.configLocations = new String[locations.length];
for (int i = 0; i < locations.length; i++) {
this.configLocations[i] = resolvePath(locations[i]).trim();
}
}
else {
this.configLocations = null;
}
}这是实现就是在：AbstractRefreshableConfigApplicationContext中，我们发先这个this.configLocations属性已经被赋值了。
Ok进入第二个判断:reader.loadBeanDefinitions(configLocations);
@Override
public int loadBeanDefinitions(String... locations) throws BeanDefinitionStoreException {
Assert.notNull(locations, "Location array must not be null");
int counter = 0;
for (String location : locations) {
counter += loadBeanDefinitions(location);
}
return counter;
}在XmlBeanDefinitionReader 的父类AbstractBeanDefinitionReader中定义的。
@Override
public int loadBeanDefinitions(String location) throws BeanDefinitionStoreException {
return loadBeanDefinitions(location, null);
}
public int loadBeanDefinitions(String location, Set<Resource> actualResources) throws BeanDefinitionStoreException {
ResourceLoader resourceLoader = getResourceLoader();
if (resourceLoader == null) {
throw new BeanDefinitionStoreException(
"Cannot import bean definitions from location [" + location + "]: no ResourceLoader available");
}
if (resourceLoader instanceof ResourcePatternResolver) {
// Resource pattern matching available.
try {
Resource[] resources = ((ResourcePatternResolver) resourceLoader).getResources(location);
int loadCount = loadBeanDefinitions(resources);
if (actualResources != null) {
for (Resource resource : resources) {
actualResources.add(resource);
}
}
if (logger.isDebugEnabled()) {
logger.debug("Loaded " + loadCount + " bean definitions from location pattern [" + location + "]");
}
return loadCount;
}
catch (IOException ex) {
throw new BeanDefinitionStoreException(
"Could not resolve bean definition resource pattern [" + location + "]", ex);
}
}
else {
// Can only load single resources by absolute URL.
Resource resource = resourceLoader.getResource(location);
int loadCount = loadBeanDefinitions(resource);
if (actualResources != null) {
actualResources.add(resource);
}
if (logger.isDebugEnabled()) {
logger.debug("Loaded " + loadCount + " bean definitions from location [" + location + "]");
}
return loadCount;
}
}
这个方法ResourceLoader：ResourceLoader resourceLoader = getResourceLoader();
@Override
public ResourceLoader getResourceLoader() {
return this.resourceLoader;
}beanDefinitionReader.setResourceLoader(this);
此时我们要往回看了，我们看下这个
XmlBeanDefinitionReader beanDefinitionReader = new XmlBeanDefinitionReader(beanFactory);
beanDefinitionReader.setResourceLoader(this);这个this就是：AbstractXmlApplicationContext也是ResourcePatternResolver的子类。
所以进入到:
Resource[] resources = ((ResourcePatternResolver) resourceLoader).getResources(location);
进入到 PathMatchingResourcePatternResolver的
@Override
public Resource[] getResources(String locationPattern) throws IOException {
Assert.notNull(locationPattern, "Location pattern must not be null");
if (locationPattern.startsWith(CLASSPATH_ALL_URL_PREFIX)) {
// a class path resource (multiple resources for same name possible)
if (getPathMatcher().isPattern(locationPattern.substring(CLASSPATH_ALL_URL_PREFIX.length()))) {
// a class path resource pattern
return findPathMatchingResources(locationPattern);
}
else {
// all class path resources with the given name
return findAllClassPathResources(locationPattern.substring(CLASSPATH_ALL_URL_PREFIX.length()));
}
}
else {
// Only look for a pattern after a prefix here
// (to not get fooled by a pattern symbol in a strange prefix).
int prefixEnd = locationPattern.indexOf(":") + 1;
if (getPathMatcher().isPattern(locationPattern.substring(prefixEnd))) {
// a file pattern
return findPathMatchingResources(locationPattern);
}
else {
// a single resource with the given name
return new Resource[] {getResourceLoader().getResource(locationPattern)};
}
}
}他会进入到最后一行:
return new Resource[] {getResourceLoader().getResource(locationPattern)};
这个getResourceLoader是DefaultResourceLoader。
在DefaultResourceLoader 定义是这样的：
@Override
public Resource getResource(String location) {
Assert.notNull(location, "Location must not be null");
if (location.startsWith("/")) {
return getResourceByPath(location);
}
else if (location.startsWith(CLASSPATH_URL_PREFIX)) {
return new ClassPathResource(location.substring(CLASSPATH_URL_PREFIX.length()), getClassLoader());
}
else {
try {
// Try to parse the location as a URL...
URL url = new URL(location);
return new UrlResource(url);
}
catch (MalformedURLException ex) {
// No URL -> resolve as resource path.
return getResourceByPath(location);
}
}
}最后一个方法：getResourceByPath
@Override
protected Resource getResourceByPath(String path) {
if (path != null && path.startsWith("/")) {
path = path.substring(1);
}
return new FileSystemContextResource(path);
}这个实现是在 FileSystemResourceLoader中
在 FilySystemXmlApplicationContext实现中有一个@Override
protected Resource getResourceByPath(String path) {
if (path != null && path.startsWith("/")) {
path = path.substring(1);
}
return new FileSystemResource(path);
}自然是使用了 FileSystemResource 定位资源。
此时定位资源结束。
二、资源的载入：
继续看这个方法：
int loadCount = loadBeanDefinitions(resources);
会到实现类:XmlBeanDefinitionReader
@Override
public int loadBeanDefinitions(Resource resource) throws BeanDefinitionStoreException {
return loadBeanDefinitions(new EncodedResource(resource));
}
public int loadBeanDefinitions(EncodedResource encodedResource) throws BeanDefinitionStoreException {
Assert.notNull(encodedResource, "EncodedResource must not be null");
if (logger.isInfoEnabled()) {
logger.info("Loading XML bean definitions from " + encodedResource.getResource());
}
Set<EncodedResource> currentResources = this.resourcesCurrentlyBeingLoaded.get();
if (currentResources == null) {
currentResources = new HashSet<EncodedResource>(4);
this.resourcesCurrentlyBeingLoaded.set(currentResources);
}
if (!currentResources.add(encodedResource)) {
throw new BeanDefinitionStoreException(
"Detected cyclic loading of " + encodedResource + " - check your import definitions!");
}
try {
InputStream inputStream = encodedResource.getResource().getInputStream();
try {
InputSource inputSource = new InputSource(inputStream);
if (encodedResource.getEncoding() != null) {
inputSource.setEncoding(encodedResource.getEncoding());
}
return doLoadBeanDefinitions(inputSource, encodedResource.getResource());
}
finally {
inputStream.close();
}
}
catch (IOException ex) {
throw new BeanDefinitionStoreException(
"IOException parsing XML document from " + encodedResource.getResource(), ex);
}
finally {
currentResources.remove(encodedResource);
if (currentResources.isEmpty()) {
this.resourcesCurrentlyBeingLoaded.remove();
}
}
}
doLoadBeanDefinitions(inputSource, encodedResource.getResource());
protected int doLoadBeanDefinitions(InputSource inputSource, Resource resource)
throws BeanDefinitionStoreException {
try {
Document doc = doLoadDocument(inputSource, resource);
return registerBeanDefinitions(doc, resource);
}
catch (BeanDefinitionStoreException ex) {
throw ex;
}
catch (SAXParseException ex) {
.......
}
我们发现他是构造了Document 去读取xml文档。后面的代码就是使用Document读取文档。我们关心的是，Spring的BeanDefinition是如何按照Spring bean语义要求进行解析，并转化为Spring内部数据结构的。
解析bean
registerBeanDefinitions(doc, resource);
public int registerBeanDefinitions(Document doc, Resource resource) throws BeanDefinitionStoreException {
BeanDefinitionDocumentReader documentReader = createBeanDefinitionDocumentReader();
int countBefore = getRegistry().getBeanDefinitionCount();
documentReader.registerBeanDefinitions(doc, createReaderContext(resource));
return getRegistry().getBeanDefinitionCount() - countBefore;
}我们看下这个方法：
documentReader.registerBeanDefinitions(doc, createReaderContext(resource));
他会处理xml文档，并且将xml的定义bean转为BeanDefinition，这个过程也是蛮复杂的，不过代码不是很难理解。我们只看下这个最为基本的将xml转为BeanDefinition的真是面目：
public AbstractBeanDefinition parseBeanDefinitionElement(
Element ele, String beanName, BeanDefinition containingBean) {
this.parseState.push(new BeanEntry(beanName));
String className = null;
if (ele.hasAttribute(CLASS_ATTRIBUTE)) {
className = ele.getAttribute(CLASS_ATTRIBUTE).trim();
}
try {
String parent = null;
if (ele.hasAttribute(PARENT_ATTRIBUTE)) {
parent = ele.getAttribute(PARENT_ATTRIBUTE);
}
AbstractBeanDefinition bd = createBeanDefinition(className, parent);
parseBeanDefinitionAttributes(ele, beanName, containingBean, bd);
bd.setDescription(DomUtils.getChildElementValueByTagName(ele, DESCRIPTION_ELEMENT));
parseMetaElements(ele, bd);
parseLookupOverrideSubElements(ele, bd.getMethodOverrides());
parseReplacedMethodSubElements(ele, bd.getMethodOverrides());
parseConstructorArgElements(ele, bd);
parsePropertyElements(ele, bd);
parseQualifierElements(ele, bd);
bd.setResource(this.readerContext.getResource());
bd.setSource(extractSource(ele));
return bd;
}
catch (ClassNotFoundException ex) {
error("Bean class [" + className + "] not found", ele, ex);
}
catch (NoClassDefFoundError err) {
error("Class that bean class [" + className + "] depends on not found", ele, err);
}
catch (Throwable ex) {
error("Unexpected failure during bean definition parsing", ele, ex);
}
finally {
this.parseState.pop();
}
return null;
}在这一部分，就是对 的处理，对Spring定义的常见的属性：init-method、destory-method和Factory-method的处理，还有lazyinit的处理，对attribute、属性、构造方法等都会设置到BeanDefinition中。
三、注册
Spring 已经将文件定义的Bean解析为BeanDefinition了，下面就是注册了。注册就是将这些beanDefinition 载入到beanFactory中的HashMap中。我们使用DefaultListablebeanFactory,我们看下这个HashMap的定义：
private final Map
@Override
public void registerBeanDefinition(String beanName, BeanDefinition beanDefinition)
throws BeanDefinitionStoreException {
Assert.hasText(beanName, "Bean name must not be empty");
Assert.notNull(beanDefinition, "BeanDefinition must not be null");
if (beanDefinition instanceof AbstractBeanDefinition) {
try {
((AbstractBeanDefinition) beanDefinition).validate();
}
catch (BeanDefinitionValidationException ex) {
throw new BeanDefinitionStoreException(beanDefinition.getResourceDescription(), beanName,
"Validation of bean definition failed", ex);
}
}
BeanDefinition oldBeanDefinition;
oldBeanDefinition = this.beanDefinitionMap.get(beanName);
if (oldBeanDefinition != null) {
if (!isAllowBeanDefinitionOverriding()) {
throw new BeanDefinitionStoreException(beanDefinition.getResourceDescription(), beanName,
"Cannot register bean definition [" + beanDefinition + "] for bean '" + beanName +
"': There is already [" + oldBeanDefinition + "] bound.");
}
else if (oldBeanDefinition.getRole() < beanDefinition.getRole()) {
// e.g. was ROLE_APPLICATION, now overriding with ROLE_SUPPORT or ROLE_INFRASTRUCTURE
if (this.logger.isWarnEnabled()) {
this.logger.warn("Overriding user-defined bean definition for bean '" + beanName +
"' with a framework-generated bean definition: replacing [" +
oldBeanDefinition + "] with [" + beanDefinition + "]");
}
}
else if (!beanDefinition.equals(oldBeanDefinition)) {
if (this.logger.isInfoEnabled()) {
this.logger.info("Overriding bean definition for bean '" + beanName +
"' with a different definition: replacing [" + oldBeanDefinition +
"] with [" + beanDefinition + "]");
}
}
else {
if (this.logger.isDebugEnabled()) {
this.logger.debug("Overriding bean definition for bean '" + beanName +
"' with an equivalent definition: replacing [" + oldBeanDefinition +
"] with [" + beanDefinition + "]");
}
}
this.beanDefinitionMap.put(beanName, beanDefinition);
}
else {
if (hasBeanCreationStarted()) {
// Cannot modify startup-time collection elements anymore (for stable iteration)
synchronized (this.beanDefinitionMap) {
this.beanDefinitionMap.put(beanName, beanDefinition);
List<String> updatedDefinitions = new ArrayList<String>(this.beanDefinitionNames.size() + 1);
updatedDefinitions.addAll(this.beanDefinitionNames);
updatedDefinitions.add(beanName);
this.beanDefinitionNames = updatedDefinitions;
if (this.manualSingletonNames.contains(beanName)) {
Set<String> updatedSingletons = new LinkedHashSet<String>(this.manualSingletonNames);
updatedSingletons.remove(beanName);
this.manualSingletonNames = updatedSingletons;
}
}
}
else {
// Still in startup registration phase
this.beanDefinitionMap.put(beanName, beanDefinition);
this.beanDefinitionNames.add(beanName);
this.manualSingletonNames.remove(beanName);
}
this.frozenBeanDefinitionNames = null;
}
if (oldBeanDefinition != null || containsSingleton(beanName)) {
resetBeanDefinition(beanName);
}
}在这个过程中，有一个allowBeanDefinitionOverriding的配置，他用来处理同名的BeanDefinition。如果遇到同名的BeanDefinition已经注册，并且又不允许覆盖，那么就会与异常抛出。
OK结束。后面我们将看 IOC容器的依赖注入的实现。
扫一扫
689
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
