The registration of BeanProcessor and BeanFactoryPostProcessor, which plays an important role in AOP and property place holders, needs the explicit code writing that makes it inconvenient to work with. Developers don't want to write code that supports internationalization. The event publication to handle AOP integration is unavoidable. For all of these, the simple solution is to expand the services provided by BeanFactory with ApplicationContext. ApplicationContext is not a replacement of BeanFactory, but it's an extension for enterprise-specific solutions and more advanced mechanisms for bean configuration.

Let's take a look at the implementations.