Let us now apply the JavaConfig specification in building the Spring context definition:

1. To get rid of the usual Maven bugs, immediately open the pom.xml of ch02-jc and add <properties>, <dependencies>, and <repositories>, equivalent to what was added in the Implementing the Spring Container using XML recipe.
2. Since the time Servlet 3.0 specification was implemented, servlet containers can now support projects without using web.xml. This is done by implementing the handler abstract class called org.springframework.web.WebApplicationInitializer to programmatically configure ServletContext. Create a SpringWebInitializer class and override its onStartup() method without any implementation yet:

public class SpringWebInitializer implements 
   WebApplicationInitializer { 
     
     @Override 
     public void onStartup(ServletContext container) throws 
         ServletException { 
       } 
} 

3. The lines in Step 2 will generate some runtime errors until you add the following Maven dependency:

<dependency> 
  <groupId>org.springframework</groupId> 
  <artifactId>spring-web</artifactId> 
  <version>${spring.version}</version> 
</dependency>

4. In pom.xml, disable the <failOnMissingWebXml> and add the same Tomcat Maven plugin for the deployment used in Chapter 1, Getting Started with Spring.

5. Now, create a class named BeanConfig, the ApplicationContext definition, with a class-level annotation @Configuration. The class must be inside the org.packt.starter.ioc.context package and must be an empty class at the moment:

@Configuration 
public class BeanConfig {   } 

6. Save all the files and clean and build the Maven project.