BeanFactory指的是在运行时调用getBean()方法后延迟实例化bean对象的spring容器。

ApplicationContext指的是spring框架，它在部署期间主动实例化bean对象，而不在运行时调用getBean()方法。

我的六分钱:

BeanFactory and ApplicationContext both are interfaces where ApplicationContext extends BeanFactory. So ApplicationContext is a child interface and BeanFactory is the parent interface. In other words, ApplicationContext has all the features of BeanFactory and it has some additional features that are not present in BeanFactory. BeanFactory loads beans on-demand that is Lazy Loading whereas ApplicationContext loads all beans at startup that is Eager Loading. BeanFactory does not support annotations whereas ApplicationContext supports annotations. ApplicationContext has additional features that are not present in BeanFactory: Internationalization, Event Publishing, AOP features. BeanFactory only supports two scopes — Singleton and Prototype whereas ApplicationContext supports all bean scopes. BeanFactory does not register BeanFactoryPostProcessor and BeanPostProcessor automatically whereas ApplicationContext automatically registers them.

Bean工厂的特性矩阵vs来自spring文档的应用程序上下文

beanfactory和ApplicationContext功能的截图

在实时场景中，Spring IOC核心容器(BeanFactory)和高级J2EE容器(ApplicationContext)之间的区别如下。

BeanFactory will create objects for the beans (i.e., for POJO classes) mentioned in the spring.xml file (<bean></bean>) only when you call the .getBean() method, but whereas ApplicationContext creates the objects for all the beans (<bean></bean> if its scope is not explicitly mentioned as "Prototype") configured in the spring.xml while loading the spring.xml file itself. BeanFactory: (Lazy container because it creates the objects for the beans only when you explicitly call from the user/main class) /* * Using core Container - Lazy container - Because it creates the bean objects On-Demand */ //creating a resource Resource r = (Resource) new ClassPathResource("com.spring.resources/spring.xml"); //creating BeanFactory BeanFactory factory=new XmlBeanFactory(r); //Getting the bean for the POJO class "HelloWorld.java" HelloWorld worldObj1 = (HelloWorld) factory.getBean("test"); ApplicationContext: (Eager container because of creating the objects of all singleton beans while loading the spring.xml file itself) ApplicationContext context = new ClassPathXmlApplicationContext("com/ioc/constructorDI/resources/spring.xml"); Technically, using ApplicationContext is recommended because in real-time applications, the bean objects will be created while the application is getting started in the server itself. This reduces the response time for the user request as the objects are already available to respond.

Spring提供两种IOC容器，一种是XMLBeanFactory，另一种是ApplicationContext。

通过完整路径加载的FileSystemXmlApplicationContext bean。 通过CLASSPATH加载的bean XMLWebApplicationContext和AnnotationConfigWebApplicationContext bean通过web应用程序上下文加载。 从基于Annotation的配置中加载Spring bean。

例子:

ApplicationContext applicationContext = new AnnotationConfigApplicationContext(BeansConfiguration.class);

ApplicationContext是由web.xml中定义的ContextLoaderListener或ContextLoaderServlet和struts-config.xml中定义的ContextLoaderPlugin初始化的容器。

注意:XmlBeanFactory从Spring 3.1开始已弃用，取而代之的是DefaultListableBeanFactory和XmlBeanDefinitionReader。

在大多数情况下，首选ApplicationContext，除非需要节省资源，比如在移动应用程序上。

我不确定是否依赖于XML格式，但我非常确定ApplicationContext最常见的实现是XML实现，例如ClassPathXmlApplicationContext、XmlWebApplicationContext和FileSystemXmlApplicationContext。我只用过这三个。

如果您正在开发web应用程序，可以肯定地说，您将需要使用XmlWebApplicationContext。

如果您希望bean能够感知Spring，您可以让它们为此实现BeanFactoryAware和/或ApplicationContextAware，因此您可以使用BeanFactory或ApplicationContext并选择实现哪个接口。