Introducing Spring Framework

Chapter 19 ■ Spring Boot, Simplifying Everything
}
@Override
protected SpringApplicationBuilder configure(SpringApplicationBuilder application) {
return application.sources(MyDocumentsWebApp.class);
}
Listing 19-6 shows the new class. You are now extending from the SpringBootServletInitializer class and you
are overriding a configure method. In this method, you are returning an application that will tell Spring Boot how
to initialize all web-related files. Also, note that you are using the @Configuration, @EnableAutoConfiguration, and
@ComponentScan annotations. These annotations are essential for Spring Boot; they’re the way it looks for all of the
necessary components for the web application.
Before in the JAR application (Listing 19-4), Spring Boot recognized that it would be a JAR application because it
had a main method and it was executing the SpringApplication.run method. This time, Spring Boot will identify this
application as a web app because you are extending from the SpringBootServletInitializer class and overriding
the configure method, and it will wire everything up so it can run on any Java web container.
The following command will create the WAR file in the build/libs folder:
gradle clean :ch19:build
Now you can deploy the WAR file on any application server or Java web container. If you are deploying in a
Tomcat-like server, you need to remember that the context by default is the name of the WAR, so the URL will be
http://localhost:8080/ch19-spring-boot-0.1.0/documents.
Spring Boot À La Groovy
Spring Boot also plays well with Groovy, so you are going to create just a subset of the My Documents Spring application,
based on Groovy scripts—only the access to the in-memory database. See Listing 19-7 for the model.groovy file.
Listing 19-7. model.groovy
class Document {
String documentId
String name
Type type
String location
String description
Date created
Date modified
}
class Type {
String typeId
String name
String desc
String extension
}
272