Difference Between ApplicationContext and WebApplicationContext in Spring MVC
Last Updated : 01 Apr, 2022
Spring MVC framework enables separation of modules namely Model, View, and Controller, and seamlessly handles the application integration. This enables the developer to create complex applications also using plain Java Classes. The model object can be passed between view and controller using maps.
What is ApplicationContext?
Spring IoC container is responsible for instantiating, wiring, configuring, and managing the entire life cycle of objects. BeanFactory and ApplicationContext represent the Spring IoC Containers. ApplicationContext is the sub-interface of BeanFactory. BeanFactory provides basic functionalities and is recommended to use for lightweight applications like mobile and applets. ApplicationContext provides basic features in addition to enterprise-specific functionalities which are as follows:
- Publishing events to registered listeners by resolving property files.
- Methods for accessing application components.
- Supports Internationalization.
- Loading File resources in a generic fashion.
Must Read - Spring – ApplicationContext
What is WebApplicationContext?
WebApplicationContext in Spring is a web-aware ApplicationContext i.e it has Servlet Context information. In a single web application, there can be multiple WebApplicationContext. That means each DispatcherServlet is associated with a single WebApplicationContext. The WebApplicationContext configuration file *-servlet.xml is specific to the DispatcherServlet and a web application can have more than one DispatcherServlet configured to handle the requests and each DispatcherServlet would have a separate *-servlet.xml file to configure.
Must Read - WebApplicationContext in Spring MVC
Difference Between ApplicationContext and WebApplicationContext in Spring MVC
Factor 1: ApplicationContext is used to create standalone applications. But for the web applications, we have to deal with a container called WebApplicationContext.
A. Standalone App
// Creating container objects manually ApplicationContext context = new ClassPathXmlApplicationContext("beans.xml");// Destroying container object manually context.close();
B. Web App
You don't need to create and destroy the container object. The container object will be created automatically with the server startup and destroyed when we stop the server.
Factor 2: One more interesting difference is both ApplicationContext and WebApplicationContext are the spring containers where WebApplicationContext is the child of the ApplicationContext interface.
public interface WebApplicationContext extends ApplicationContext { ............... }After having a brief idea about the purpose and standalone app and web app in order, to sum up, the differences between ApplicationContext and WebApplicationContext, it is depicted in tabular manner as shown below:
ApplicationContext | WebApplicationContext |
|---|
| ApplicationContext is used to create standalone applications. | WebApplicationContext is used to create web applications. |
| ApplicationContext is the parent of the WebApplicationContext interface. | WebApplicationContext is the child of the ApplicationContext interface. |
| In the case of ApplicationContext, we have to create and destroy the container objects manually. | But in the case of WebApplicationContext, we don't need to create and destroy the container object. The container object will be created automatically. |
| There is always a single ApplicationContext in an application. | There can be multiple WebApplicationContexts for each of the dispatcher servlets. |
| ApplicationContext represents the Spring IoC Containers and it is the sub-interface of BeanFactory. | WebApplicationContext in Spring is a web-aware ApplicationContext i.e it has Servlet Context information. |
| ApplicationContext is used to inject all the middle-tier beans (Services, DAOs) which are instantiated using the "ContextLoaderListener" class configured in web.xml. | WebApplicationContext is used to deal with the web-related components such as controllers and view resolvers, which is configured using "DispatcherServlet". |
Similar Reads
ViewResolver in Spring MVC Spring MVC is a powerful Web MVC Framework for building web applications. It provides a structured way to develop web applications by separating concerns into Model, View, and Controller. One of the key features of Spring MVC is the ViewResolver, which enables you to render models in the browser wit
7 min read
How to Create Your First Model in Spring MVC? Spring MVC is a powerful Web MVC framework for building web applications. It is designed around the Model-View-Controller (MVC) pattern, which separates the application into three main components:Model: Represents the data of the application. It can be a single object or a collection of objects.View
6 min read
How to Create Your First View in Spring MVC? Spring MVC is a powerful Web MVC Framework for building web applications. It is designed around the Model-View-Controller (MVC) pattern, which separates the application into three main components:Model: Represents the data of the application. It can be a single object or a collection of objects.View
5 min read
Spring MVC CRUD with Example In this article, we will explore how to build a Spring MVC CRUD application from scratch. CRUD stands for Create, Read/Retrieve, Update, and Delete. These are the four basic operations to create any type of project. Spring MVC is a popular framework for building web applications. Spring MVC follows
7 min read
Create and Run Your First Spring MVC Controller in Eclipse/Spring Tool Suite Spring MVC framework enables the separation of modules, namely Model, View, and Controller, and seamlessly handles the application integration. This enables the developer to create complex applications also using plain Java classes. The model object can be passed between the view and the controller
5 min read
What is Dispatcher Servlet in Spring? Spring is one of the most popular Java EE frameworks. It is an open-source lightweight framework that allows Java EE 7 developers to build simple, reliable, and scalable enterprise applications. This framework mainly focuses on providing various ways to help you manage your business objects. It made
6 min read
Spring - Shortcut to Create Dispatcher Servlet in Eclipse/Spring Tool Suite Eclipse is an Integrated Development Environment (IDE) used in computer programming. It includes a base workspace and an extensible plug-in system for customizing the environment. It is the second-most-popular IDE for Java development. Eclipse is written mostly in Java and its primary use is for dev
4 min read
WebApplicationContext in Spring MVC Spring MVC framework enables separation of modules namely Model, View, and Controller, and seamlessly handles the application integration. This enables the developer to create complex applications also using plain java classes. The model object can be passed between view and controller using maps. T
7 min read
Spring - Multi Action Controller with Example Spring is one of the most popular Java EE frameworks. It is an open-source lightweight framework that allows Java EE 7 developers to build simple, reliable, and scalable enterprise applications. This framework mainly focuses on providing various ways to help you manage your business objects. It made
4 min read
Spring MVC - Exception Handling Prerequisites: Spring MVC When something goes wrong with your application, the server displays an exception page defining the type of exception, the server-generated exception page is not user-friendly. Spring MVC provides exception handling for your web application to make sure you are sending your
6 min read