Partner – Microsoft – NPI (cat= Spring)
announcement - icon

Azure Spring Apps is a fully managed service from Microsoft (built in collaboration with VMware), focused on building and deploying Spring Boot applications on Azure Cloud without worrying about Kubernetes.

And, the Enterprise plan comes with some interesting features, such as commercial Spring runtime support, a 99.95% SLA and some deep discounts (up to 47%) when you are ready for production.

>> Learn more and deploy your first Spring Boot app to Azure.

You can also ask questions and leave feedback on the Azure Spring Apps GitHub page.

1. Introduction

When developing a Spring application, it is necessary to tell the framework where to look for beans. When the application starts, the framework locates and registers all of them for further execution. Similarly, we need to define the mapping where all incoming requests to the web application will be processed.

All the Java web frameworks are built on top of servlet api. In a web application, three files play a vital role. Usually, we chain them in order as: web.xml -> applicationContext.xml -> spring-servlet.xml

In this article, we’ll look at the differences between the applicationContext and spring-servlet.

2. applicationContext.xml

Inversion of control (IoC) is the core of the Spring framework. In IoC enabled framework, usually, a container is responsible for instantiating, creating, and deleting objects. In Spring, applicationContext plays the role of an IoC container.

When developing a standard J2EE application, we declare the ContextLoaderListener in the web.xml file. In addition, a contextConfigLocation is also defined to indicate the XML configuration file.


When the application starts, the Spring loads this configuration file and uses it to create a WebApplicationContext object. In the absence of contextConfigLocation, by default, the system will look for/WEB-INF/applicationContext.xml to load.

In short, applicationContext is the central interface in Spring. It provides configuration information for an application.

In this file, we provide the configurations related to the application. Usually, those are the basic data source, property place holder file, and message source for project localization, among other enhancements.

Let’s look at the sample file:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

    <context:property-placeholder location="classpath:/" />

    <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">
        <property name="driverClassName" value="${jdbc.driverClassName}" />
        <property name="url" value="${jdbc.url}" />
        <property name="username" value="${jdbc.username}" />
        <property name="password" value="${jdbc.password}" />
        <property name="initialSize" value="5" />
        <property name="maxActive" value="10" />

    <bean id="messageSource"
        <property name="basename" value="messages" />

ApplicationContext is a complete superset of the BeanFactory interface and, hence, provides all the functionalities of BeanFactory. It also provides the integrated lifecycle management, automatic registration of BeanPostProcessor and BeanFactoryPostProcessor, convenient access to MessageSource, and publication of ApplicationEvent.

3. spring-servlet.xml

In Spring, a single front servlet takes the incoming requests and delegates them to appropriate controller methods. The front servlet, based on a Front controller design pattern, handles all the HTTP requests of a particular web application. This front servlet has all the controls over incoming requests.

Similarly, spring-servlet acts as a front controller servlet and provides a single entry point. It takes the incoming URI. Behind the scenes, it uses HandlerMapping implementation to define a mapping between requests and handler objects.

Let’s look at the sample code:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns=""

    <mvc:annotation-driven />
    <context:component-scan base-package="com.baeldung.controller" />

    <bean id="viewResolver"
	<property name="viewClass"
          value="org.springframework.web.servlet.view.JstlView" />
	<property name="prefix" value="/WEB-INF/jsp/" />
	<property name="suffix" value=".jsp" />


4. applicationContext.xml vs. spring-servlet.xml

Let’s look at the summarize view:

Feature applicationContext.xml spring-servlet.xml
Framework It is part of the Spring framework. It is part of the Spring MVC framework.
Purpose A container that defines spring beans. A front controller that processes the incoming requests.
Scope It defines the beans that are shared among all servlets. It defines servlet-specific beans only.
Manages It manages global things like datasource, and connection factories are defined in it. Conversely, Only web-related things like controllers and viewresolver will be defined in it.
References It cannot access the beans of spring-servlet. It can access the beans defined in applicationContext.
Sharing Properties common to the whole application will go here. Properties that are specific to one servlet only will go here.
Scanning We define the filters to include/exclude packages. We declare the component scans for controllers.
Occurrence It is common to define multiple context files in an application. Similarly, we can define multiple files in a web application.
Loading The file applicationContext.xml is loaded by ContextLoaderListener. The file spring-servlet.xml is loaded by DispatcherServlet.
Required Optional Mandatory

5. Conclusion

In this tutorial, we learned about the applicationContext and spring-servlet files. Then, we discussed their role and responsibilities in a Spring application. In the end, we looked at the differences between them.

Course – LS (cat=Spring)

Get started with Spring and Spring Boot, through the Learn Spring course:

res – REST with Spring (eBook) (everywhere)
Comments are open for 30 days after publishing a post. For any issues past this date, use the Contact form on the site.