Springboot事件和bean的生命周期执行机制

最新推荐文章于 2024-07-17 14:45:15 发布
最新推荐文章于 2024-07-17 14:45:15 发布
阅读量455 收藏
点赞数
分类专栏： springboot 文章标签： spring boot
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/guntun8987/article/details/129789174
版权

@PostConstruct执行机制

进入SpringApplication#run(java.lang.String…)

public ConfigurableApplicationContext run(String... args) {
	StopWatch stopWatch = new StopWatch();
	stopWatch.start();
	ConfigurableApplicationContext context = null;
	configureHeadlessProperty();
	SpringApplicationRunListeners listeners = getRunListeners(args);
	listeners.starting();
	try {
		ApplicationArguments applicationArguments = new DefaultApplicationArguments(args);
		ConfigurableEnvironment environment = prepareEnvironment(listeners, applicationArguments);
		configureIgnoreBeanInfo(environment);
		Banner printedBanner = printBanner(environment);
		context = createApplicationContext();
		prepareContext(context, environment, listeners, applicationArguments, printedBanner);
		//这里进入就会执行经典的refresh方法进行容器创建工作
		refreshContext(context);
		afterRefresh(context, applicationArguments);
		stopWatch.stop();
		if (this.logStartupInfo) {
			new StartupInfoLogger(this.mainApplicationClass).logStarted(getApplicationLog(), stopWatch);
		}
		listeners.started(context);
		callRunners(context, applicationArguments);
	}
	catch (Throwable ex) {
		handleRunFailure(context, ex, listeners);
		throw new IllegalStateException(ex);
	}

	try {
		listeners.running(context);
	}
	catch (Throwable ex) {
		handleRunFailure(context, ex, null);
		throw new IllegalStateException(ex);
	}
	return context;
}

进入AbstractApplicationContext#refresh

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();

			// 在这里将非懒加载的bean进行创建
			finishBeanFactoryInitialization(beanFactory);

			// Last step: publish corresponding event.
			finishRefresh();
		}

		catch (BeansException ex) {
			if (logger.isWarnEnabled()) {
				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;
		}

		finally {
			// Reset common introspection caches in Spring's core, since we
			// might not ever need metadata for singleton beans anymore...
			resetCommonCaches();
		}
	}
}

进入AbstractApplicationContext#finishBeanFactoryInitialization

AbstractApplicationContext#finishBeanFactoryInitialization
protected void finishBeanFactoryInitialization(ConfigurableListableBeanFactory beanFactory) {
	// Initialize conversion service for this context.
	if (beanFactory.containsBean(CONVERSION_SERVICE_BEAN_NAME) &&
			beanFactory.isTypeMatch(CONVERSION_SERVICE_BEAN_NAME, ConversionService.class)) {
		beanFactory.setConversionService(
				beanFactory.getBean(CONVERSION_SERVICE_BEAN_NAME, ConversionService.class));
	}

	// Register a default embedded value resolver if no BeanFactoryPostProcessor
	// (such as a PropertySourcesPlaceholderConfigurer bean) registered any before:
	// at this point, primarily for resolution in annotation attribute values.
	if (!beanFactory.hasEmbeddedValueResolver()) {
		beanFactory.addEmbeddedValueResolver(strVal -> getEnvironment().resolvePlaceholders(strVal));
	}

	// Initialize LoadTimeWeaverAware beans early to allow for registering their transformers early.
	String[] weaverAwareNames = beanFactory.getBeanNamesForType(LoadTimeWeaverAware.class, false, false);
	for (String weaverAwareName : weaverAwareNames) {
		getBean(weaverAwareName);
	}

	// Stop using the temporary ClassLoader for type matching.
	beanFactory.setTempClassLoader(null);

	// Allow for caching all bean definition metadata, not expecting further changes.
	beanFactory.freezeConfiguration();

	// 将非单例的对象进行真正的创建
	beanFactory.preInstantiateSingletons();
}

在beanFactory.preInstantiateSingletons()中就是循环的创建将非单例的对象，此方法会一直调用到AbstractAutowireCapableBeanFactory#doCreateBean

AbstractAutowireCapableBeanFactory#doCreateBean
protected Object doCreateBean(String beanName, RootBeanDefinition mbd, @Nullable Object[] args)
		throws BeanCreationException {

	// Instantiate the bean.
	BeanWrapper instanceWrapper = null;
	if (mbd.isSingleton()) {
		instanceWrapper = this.factoryBeanInstanceCache.remove(beanName);
	}
	//真正的创建对象
	if (instanceWrapper == null) {
		instanceWrapper = createBeanInstance(beanName, mbd, args);
	}
	Object bean = instanceWrapper.getWrappedInstance();
	Class<?> beanType = instanceWrapper.getWrappedClass();
	if (beanType != NullBean.class) {
		mbd.resolvedTargetType = beanType;
	}

	// Allow post-processors to modify the merged bean definition.
	synchronized (mbd.postProcessingLock) {
		if (!mbd.postProcessed) {
			try {
				applyMergedBeanDefinitionPostProcessors(mbd, beanType, beanName);
			}
			catch (Throwable ex) {
				throw new BeanCreationException(mbd.getResourceDescription(), beanName,
						"Post-processing of merged bean definition failed", ex);
			}
			mbd.postProcessed = true;
		}
	}

	// Eagerly cache singletons to be able to resolve circular references
	// even when triggered by lifecycle interfaces like BeanFactoryAware.
	boolean earlySingletonExposure = (mbd.isSingleton() && this.allowCircularReferences &&
			isSingletonCurrentlyInCreation(beanName));
	if (earlySingletonExposure) {
		if (logger.isTraceEnabled()) {
			logger.trace("Eagerly caching bean '" + beanName +
					"' to allow for resolving potential circular references");
		}
		addSingletonFactory(beanName, () -> getEarlyBeanReference(beanName, mbd, bean));
	}

	// Initialize the bean instance.
	Object exposedObject = bean;
	try {
		populateBean(beanName, mbd, instanceWrapper);
		//生命周期方法的执行 @PostConstruct就是在此执行的
		exposedObject = initializeBean(beanName, exposedObject, mbd);
	}
	catch (Throwable ex) {
		if (ex instanceof BeanCreationException && beanName.equals(((BeanCreationException) ex).getBeanName())) {
			throw (BeanCreationException) ex;
		}
		else {
			throw new BeanCreationException(
					mbd.getResourceDescription(), beanName, "Initialization of bean failed", ex);
		}
	}

	if (earlySingletonExposure) {
		Object earlySingletonReference = getSingleton(beanName, false);
		if (earlySingletonReference != null) {
			if (exposedObject == bean) {
				exposedObject = earlySingletonReference;
			}
			else if (!this.allowRawInjectionDespiteWrapping && hasDependentBean(beanName)) {
				String[] dependentBeans = getDependentBeans(beanName);
				Set<String> actualDependentBeans = new LinkedHashSet<>(dependentBeans.length);
				for (String dependentBean : dependentBeans) {
					if (!removeSingletonIfCreatedForTypeCheckOnly(dependentBean)) {
						actualDependentBeans.add(dependentBean);
					}
				}
				if (!actualDependentBeans.isEmpty()) {
					throw new BeanCurrentlyInCreationException(beanName,
							"Bean with name '" + beanName + "' has been injected into other beans [" +
							StringUtils.collectionToCommaDelimitedString(actualDependentBeans) +
							"] in its raw version as part of a circular reference, but has eventually been " +
							"wrapped. This means that said other beans do not use the final version of the " +
							"bean. This is often the result of over-eager type matching - consider using " +
							"'getBeanNamesForType' with the 'allowEagerInit' flag turned off, for example.");
				}
			}
		}
	}

	// Register bean as disposable.
	try {
		registerDisposableBeanIfNecessary(beanName, bean, mbd);
	}
	catch (BeanDefinitionValidationException ex) {
		throw new BeanCreationException(
				mbd.getResourceDescription(), beanName, "Invalid destruction signature", ex);
	}

	return exposedObject;
}

AbstractAutowireCapableBeanFactory#initializeBean其中的执行之一就是@PostConstruct

AbstractAutowireCapableBeanFactory#initializeBean
protected Object initializeBean(String beanName, Object bean, @Nullable RootBeanDefinition mbd) {
	if (System.getSecurityManager() != null) {
		AccessController.doPrivileged((PrivilegedAction<Object>) () -> {
			invokeAwareMethods(beanName, bean);
			return null;
		}, getAccessControlContext());
	}
	else {
		invokeAwareMethods(beanName, bean);
	}

	Object wrappedBean = bean;
	if (mbd == null || !mbd.isSynthetic()) {
		//循环执行PostProcessors后置处理器的postProcessBeforeInitialization方法，@PostConstruct就是在这里执行的
		wrappedBean = applyBeanPostProcessorsBeforeInitialization(wrappedBean, beanName);
	}

	try {
		invokeInitMethods(beanName, wrappedBean, mbd);
	}
	catch (Throwable ex) {
		throw new BeanCreationException(
				(mbd != null ? mbd.getResourceDescription() : null),
				beanName, "Invocation of init method failed", ex);
	}
	if (mbd == null || !mbd.isSynthetic()) {
		wrappedBean = applyBeanPostProcessorsAfterInitialization(wrappedBean, beanName);
	}

	return wrappedBean;
}
AbstractAutowireCapableBeanFactory#applyBeanPostProcessorsBeforeInitialization
public Object applyBeanPostProcessorsBeforeInitialization(Object existingBean, String beanName)
		throws BeansException {

	Object result = existingBean;
	for (BeanPostProcessor processor : getBeanPostProcessors()) {
		//当循环到processor=CommonAnnotationBeanPostProcessor时，点击进入分析
		Object current = processor.postProcessBeforeInitialization(result, beanName);
		if (current == null) {
			return result;
		}
		result = current;
	}
	return result;
}

CommonAnnotationBeanPostProcessor继承了InitDestroyAnnotationBeanPostProcessor，postProcessBeforeInitialization(Object bean, String beanName)方法在父类中

InitDestroyAnnotationBeanPostProcessor#postProcessBeforeInitialization
public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {
	LifecycleMetadata metadata = findLifecycleMetadata(bean.getClass());
	try {
		metadata.invokeInitMethods(bean, beanName);
	}
	catch (InvocationTargetException ex) {
		throw new BeanCreationException(beanName, "Invocation of init method failed", ex.getTargetException());
	}
	catch (Throwable ex) {
		throw new BeanCreationException(beanName, "Failed to invoke init method", ex);
	}
	return bean;
}
InitDestroyAnnotationBeanPostProcessor.LifecycleMetadata#invokeInitMethods
public void invokeInitMethods(Object target, String beanName) throws Throwable {
  Collection<LifecycleElement> checkedInitMethods = this.checkedInitMethods;
  Collection<LifecycleElement> initMethodsToIterate =
      (checkedInitMethods != null ? checkedInitMethods : this.initMethods);
  if (!initMethodsToIterate.isEmpty()) {
    for (LifecycleElement element : initMethodsToIterate) {
      if (logger.isTraceEnabled()) {
        logger.trace("Invoking init method on bean '" + beanName + "': " + element.getMethod());
      }
      //在这里反射执行带有@PostConstruct注解的方法
      element.invoke(target);
    }
  }
}

ContextRefreshedEvent事件机制

进入SpringApplication#run(java.lang.String…)

public ConfigurableApplicationContext run(String... args) {
	StopWatch stopWatch = new StopWatch();
	stopWatch.start();
	ConfigurableApplicationContext context = null;
	configureHeadlessProperty();
	SpringApplicationRunListeners listeners = getRunListeners(args);
	listeners.starting();
	try {
		ApplicationArguments applicationArguments = new DefaultApplicationArguments(args);
		ConfigurableEnvironment environment = prepareEnvironment(listeners, applicationArguments);
		configureIgnoreBeanInfo(environment);
		Banner printedBanner = printBanner(environment);
		context = createApplicationContext();
		prepareContext(context, environment, listeners, applicationArguments, printedBanner);
		//这里进入就会执行经典的refresh方法进行容器创建工作
		refreshContext(context);
		afterRefresh(context, applicationArguments);
		stopWatch.stop();
		if (this.logStartupInfo) {
			new StartupInfoLogger(this.mainApplicationClass).logStarted(getApplicationLog(), stopWatch);
		}
		listeners.started(context);
		callRunners(context, applicationArguments);
	}
	catch (Throwable ex) {
		handleRunFailure(context, ex, listeners);
		throw new IllegalStateException(ex);
	}

	try {
		listeners.running(context);
	}
	catch (Throwable ex) {
		handleRunFailure(context, ex, null);
		throw new IllegalStateException(ex);
	}
	return context;
}

进入AbstractApplicationContext#refresh

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);

			//在这个方法进行发布ContextRefreshedEvent事件
			finishRefresh();
		}

		catch (BeansException ex) {
			if (logger.isWarnEnabled()) {
				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;
		}

		finally {
			// Reset common introspection caches in Spring's core, since we
			// might not ever need metadata for singleton beans anymore...
			resetCommonCaches();
		}
	}
}
AbstractApplicationContext#finishRefresh
protected void finishRefresh() {
  // Clear context-level resource caches (such as ASM metadata from scanning).
  clearResourceCaches();

  // Initialize lifecycle processor for this context.
  initLifecycleProcessor();

  // Propagate refresh to lifecycle processor first.
  getLifecycleProcessor().onRefresh();

  // 这里进行真正的ContextRefreshedEvent事件发布
  publishEvent(new ContextRefreshedEvent(this));

  // Participate in LiveBeansView MBean, if active.
  LiveBeansView.registerApplicationContext(this);
}
AbstractApplicationContext#publishEvent
protected void publishEvent(Object event, @Nullable ResolvableType eventType) {
  Assert.notNull(event, "Event must not be null");

  // Decorate event as an ApplicationEvent if necessary
  ApplicationEvent applicationEvent;
  if (event instanceof ApplicationEvent) {
    applicationEvent = (ApplicationEvent) event;
  }
  else {
    applicationEvent = new PayloadApplicationEvent<>(this, event);
    if (eventType == null) {
      eventType = ((PayloadApplicationEvent<?>) applicationEvent).getResolvableType();
    }
  }

  // Multicast right now if possible - or lazily once the multicaster is initialized
  if (this.earlyApplicationEvents != null) {
    this.earlyApplicationEvents.add(applicationEvent);
  }
  else {
    //通过spring的applicationContext进行ContextRefreshedEvent事件发布
    getApplicationEventMulticaster().multicastEvent(applicationEvent, eventType);
  }

  // Publish event via parent context as well...
  if (this.parent != null) {
    if (this.parent instanceof AbstractApplicationContext) {
      //如果执行到这里说明是有的bean依赖了微服务Feign的接口，springboot就会生成Feign的接口的bean，
      //每个feign会有自己spring上下文容器是为了集成ribbon的配置，这里的parent就是父容器也就是springboot本身的上下文容器
      ((AbstractApplicationContext) this.parent).publishEvent(event, eventType);
    }
    else {
      this.parent.publishEvent(event);
    }
  }
}

ApplicationStartedEvent事件机制

依旧进入SpringApplication#run(java.lang.String…)

public ConfigurableApplicationContext run(String... args) {
	StopWatch stopWatch = new StopWatch();
	stopWatch.start();
	ConfigurableApplicationContext context = null;
	configureHeadlessProperty();
	SpringApplicationRunListeners listeners = getRunListeners(args);
	listeners.starting();
	try {
		ApplicationArguments applicationArguments = new DefaultApplicationArguments(args);
		ConfigurableEnvironment environment = prepareEnvironment(listeners, applicationArguments);
		configureIgnoreBeanInfo(environment);
		Banner printedBanner = printBanner(environment);
		context = createApplicationContext();
		prepareContext(context, environment, listeners, applicationArguments, printedBanner);
		refreshContext(context);
		afterRefresh(context, applicationArguments);
		stopWatch.stop();
		if (this.logStartupInfo) {
			new StartupInfoLogger(this.mainApplicationClass).logStarted(getApplicationLog(), stopWatch);
		}
    //在这里就进行ApplicationStartedEvent事件的发布
		listeners.started(context);
		callRunners(context, applicationArguments);
	}
	catch (Throwable ex) {
		handleRunFailure(context, ex, listeners);
		throw new IllegalStateException(ex);
	}

	try {
		listeners.running(context);
	}
	catch (Throwable ex) {
		handleRunFailure(context, ex, null);
		throw new IllegalStateException(ex);
	}
	return context;
}

EventPublishingRunListener#started

public void started(ConfigurableApplicationContext context) {
  //进行ApplicationStartedEvent事件的发布
  context.publishEvent(new ApplicationStartedEvent(this.application, this.args, context));
  AvailabilityChangeEvent.publish(context, LivenessState.CORRECT);
}

总结

  • 执行顺序，1 @PostConstruct执行 2 ContextRefreshedEvent事件 3 ApplicationStartedEvent事件

细节问题

在实际项目中发现ContextRefreshedEvent事件先于@PostConstruct执行，并且会执行多次。

原因

  1. 这是因为项目是Springcloud引入了Feign的微服务，当执行将所有的懒加载对象进行生成这个步骤时
  2. 如果有的bean依赖了微服务Feign的接口，springboot就会生成Feign的接口的bean
  3. 每个feign会有自己spring上下文容器是为了集成ribbon的配置，这里的parent就是父容器也就是springboot本身的上下文容器
  4. 所以只要有的bean依赖了微服务Feign的接口，在进行fegin的实际生成时会有自己的spring上下文，就会发布一遍ContextRefreshedEvent事件
阿星不是程序员
关注
专栏目录
SpringBoot 系列-事件机制详解
glmapper_2018
01-01 1563
微信公众号：glmapper工作室 掘金专栏：glmapper 微 博：疯狂的石头_henu 欢迎关注，一起学习分享技术 SpringBoot-SpringBoot中的事件机制SpringApplicationRunListenerSpringApplicationRunListenersEventPublishingRunListenerApplicationStartin...
springBoot的事件机制GenericApplicationListener用法解析
08-25
在 Spring Boot 中，事件机制是一种非常重要的机制，它允许开发者在应用程序的生命周期中执行特定的操作。GenericApplicationListener 是 Spring Boot 中的一种监听器，它可以监听应用程序中的事件，并执行相应的...
SpringBoot内置生命周期事件详解 SpringBoot源码(十)
01-20
SpringBoot中文注释项目Github地址： https://github.com/yuanmabiji/spring-boot-2.1.0.RELEASE 本篇接 SpringBoot事件监听机制源码分析(上) SpringBoot源码(九) 1 温故而知新 温故而知新，我们来简单回顾一下上篇的内容，上一篇我们分析了SpringBoot启动时广播生命周期事件的原理，现将关键步骤再浓缩总结下： 为广播SpringBoot内置生命周期事件做前期准备：1）首先加载ApplicationListener监听器实现类；2）其次加载SPI扩展类EventPublishingRunListener。
SpringBoot生命周期事件
CyberPunch's Blogs
10-26 261
SpringBoot生命周期事件 Cyberpunch 2021年10月26日 ApplicationStartingEvent 在SpringApplication启动时，Environment或容器ApplicationContext创建前触发，标志SpringApplication开始启动。 ApplicationEnviromentPreparedEvent 当SpringApplication已经开始启动且环境变量Environment已经准备好时触发，标志环境变量已经准备好了。
SpringBoot内置生命周期事件详解 SpringBoot源码(十)
qq_41490913的博客
05-03 241
SpringBoot内置生命周期事件详解 SpringBoot源码(十)
【SpringBoot】SpringBoot 生命周期及相关事件浅析 二
小水牛的博客
10-12 633
【源码】SpringBoot 生命周期及相关事件浅析 二前言版本ApplicationContextInitializedEventApplicationContextInitializedEvent 对应的监听器ApplicationPreparedEventApplicationPreparedEvent 对应的监听器ApplicationStartedEventApplicationStartedEvent 对应的监听器ApplicationReadyEventApplicationReadyEven
Spring启动生命周期
qq_31457665的博客
02-22 737
Spring Boot 应用程序的生命周期包含几个阶段，每个阶段都有特定的事件和钩子，允许开发者在应用程序的不同生命周期阶段插入自定义逻辑。Spring Boot 生命周期详解。
深入探究SpringBoot中Bean的生命周期（五）
但可以推测，与标题相关的内容应该包含了一个或多个名为"beanDemo"的示例文件，这些文件可能展示了如何在Spring Boot项目中配置和观察Bean生命周期的不同阶段。开发者可以通过查看这些"beanDemo"文件来进一步加深对...
springboot生命周期和springbean生命周期的区别是什么
09-20
在SpringBoot中，应用程序的生命周期由Spring Boot框架负责管理，它提供了一系列的事件和钩子函数，可以在不同的阶段对应用程序进行处理。通常，我们可以使用@Component注解将类标记为一个Bean，并使用@Event...
springboot bean的生命周期
04-30
Spring Boot中的Bean生命周期可以分为以下几个阶段： 1. 实例化Bean：在Spring...总之，Spring Boot的Bean生命周期包括Bean的实例化、属性注入、初始化、使用和销毁等阶段，这些阶段都经过了Spring容器的管理和控制。
springBoot的生命周期
weixin_42608299的博客
02-13 1090
Spring Boot 的生命周期主要包括以下几个阶段： 启动：当应用启动时，Spring Boot 会读取配置文件、执行自动配置类、加载应用程序上下文。 运行：当应用程序上下文加载完毕后，应用程序将开始运行，可以处理请求和提供服务。 关闭：当应用程序停止运行时，Spring Boot 会关闭应用程序上下文并销毁所有的单例 bean。 在 Spring Boot 生命周期中，你可以定义自...
Spring Boot 中，监听应用程序启动的生命周期事件的4种方法
最新发布
咖啡程序员
07-17 1475
你可以创建一个实现 ApplicationListener 接口的类，监听 ApplicationStartingEvent、ApplicationEnvironmentPreparedEvent、ApplicationPreparedEvent、ApplicationStartedEvent、ApplicationReadyEvent 等事件。");");");");");");
SpringBoot中Bean的生命周期
情怀中的释然~
02-23 1004
SpringBoot中Bean的生命周期 Bean的定义 Bean的初始化 Bean的生存期 Bean的销毁 spring通过我们的配置，如@ComponentScan定义的扫描路径去找到带有@Component的类，这个过程就是一个资源定位的过程。 一单找到了资源，那么它就开始解析，并且将定义的信息保存起来。注意此时还没有初始化Bean，也就是没有Bean的实例，它有的仅仅是Bean的定义。 ...
SpringBoot -- 事件（Application Event Listener）
Janson_Lin
10-23 280
Spring的事件为Bean与Bean之间的消息通信提供了支持，当一个Bean处理完一个任务之后，希望另外一个Bean知道并能做相应的处理，这时我们就需要让一个Bean监听当前Bean所发送的事件。 　　Spring的事件需要遵循如下流程： 自定义事件，集成ApplicationEvent。 定义事件监听器，实现ApplicationListener。 使用容器发布事件。 一、自定义事件 ...
springboot事务管理_Springboot架构解析
weixin_39774490的博客
12-08 243
Spring boot是Spring框架的一个模块，用于创建独立的，生产级的Spring基础应用程序，并且程序员的工作量最小。它是在核心弹簧框架之上开发的。spring boot背后的主要概念是避免大量的样板代码和配置来改进开发，单元测试等。在创建新的spring应用程序的情况下，我们编写了许多XML配置，服务器设置，添加依赖项等。这些配置文件是样板代码的一个例子。Spring boot避免...
springboot bean、容器的初始化，销毁及事件捕捉
彻底拆分，一切可控！
06-17 6090
文章目录1.Bean初始化后执行2.Spring容器启动后执行3.Spring 容器各个事件的回调 1.Bean初始化后执行 使用 spring 提供的 @PostConstruct 和 @PreDestroy 注解来实现对象实例的启动和销毁时要执行的代码。 package com.dada.test.config; import org.springframework.stereotype....
Springboot启动流程分析（四）：完成启动流程
bigbearxyz的博客
11-27 1127
Springboot启动过程完结篇
SpringBoot生命周期
热门推荐
SpringBoot应用最佳实践
05-29 1万+
SpringBoot应用的生命周期，整体上可以分为SpringApplication初始化阶段、SpringApplication运行阶段、SpringApplication结束阶段、SpringBoot应用退出四个阶段。
SpringBoot之Bean的使用及处理
weixin 19953181360
06-03 2352
1. SpringBoot之Bean的使用及处理 1.1引入pom依赖 <properties> <maven.compiler.source>8</maven.compiler.source> <maven.compiler.target>8</maven.compiler.target> </properties> <!--引入springboot父工程依赖-->
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值