You will need sbt which is the project builder, if on a Mac you can:
brew install sbt
To run the webapp you use sbt, although it can be a memory hog so you might want to add this to your environment
export SBT_OPTS=-XX:MaxPermSize=2048M
Then run like from within sbt
container:start
This will start the application in an embedded Jetty web container.
To build a deployable file (WAR - Web ARchive) you can run sbt and run the following command:
package
There is a plugin which will build IntelliJ project files, run sbt and run the following command
gen-idea
In my previous job at The Guardian I used Scala on various projects and enjoyed it. We employed various dependency injection (DI) frameworks from Spring, Guice and a lightweight homegrow version. Now I'm at Pivotal Labs Spring is part of the family and some recent JVM projects combined with the recent release of Spring 4 means we've been looking at how these tools can help our clients.
I think there's a natural tendency when you hear 'Spring' to think 'Java', but I wanted to show that this isn't the case anymore, and I'm going to walk through a simple web application using Scala and Spring 4. Here's the toolset I'm using here:
So first off, you'll notice I'm not using Maven or Gradle but SBT. This is the build.sbt file which outlines the name and version of the application along with the Scala version. It pulls in the webSettings from a plugin which I'll drop into in a moment. Then it outlines the dependencies, spring-mvc for the web component of the application, jetty-container is required for the complication and runtime while jetty-jsp is only required for the runtime used by the plugin.
name := "Hello World"
version := "1.0"
scalaVersion := "2.10.2"
seq(webSettings : _*)
libraryDependencies ++= Seq(
"org.springframework" % "spring-webmvc" % "4.0.0.RELEASE",
"org.eclipse.jetty" % "jetty-webapp" % "9.1.0.v20131115" % "container, compile",
"org.eclipse.jetty" % "jetty-jsp" % "9.1.0.v20131115" % "container"
)
In projects/plugins.sbt there are two plugins, one for running the web application within SBT and the other to create IntelliJ project files.
addSbtPlugin("com.earldouglas" % "xsbt-web-plugin" % "0.6.0")
addSbtPlugin("com.github.mpeltonen" % "sbt-idea" % "1.5.2")
The project uses the 'standard' Java convention of having a src folder at the root, followed by webapp which includes the web application configuration and static resources as well as the source folder called scala. Within the scala directory there is a namespaced directory structure of com/robb1e/helloworld although in Scala unlike in Java there is not a one to one mapping of file to classname. In the codebase I've included the Config class in the root of the src/scala directory to demonstrate this. But let's first head into webapp/WEB-INF/web.xml. This is the deployment descriptor from the Servlet standard.
This file is what's loaded by the servlet container and although it looks big, there's not all that going on here.
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<display-name>Scala Spring MVC 4 Web Site</display-name>
<servlet>
<servlet-name>dispatcher</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<init-param>
<param-name>contextClass</param-name>
<param-value>org.springframework.web.context.support.AnnotationConfigWebApplicationContext</param-value>
</init-param>
<init-param>
<param-name>contextConfigLocation</param-name>
<param-value>com.robb1e.helloworld.Config</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>dispatcher</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
</web-app>
The second init-param element within the servlet element defines the class with the application configuration which we'll come to shortly.
<init-param>
<param-name>contextConfigLocation</param-name>
<param-value>com.robb1e.helloworld.Config</param-value>
</init-param>
We then tell the defined servlet to serve the root path
<servlet-mapping>
<servlet-name>dispatcher</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
This configuration uses Spring annotations @ComponentScan to declare which package to look for Spring wiring to occur in. The @Bean annotation makes the viewResolver available which is required by the controller to render HTML.
package com.robb1e.helloworld
import org.springframework.context.annotation.{Bean, ComponentScan}
import org.springframework.web.servlet.view.{InternalResourceViewResolver, JstlView}
@ComponentScan(basePackages = Array("com.robb1e.helloworld"))
class Config {
@Bean
def viewResolver = {
val viewResolver = new InternalResourceViewResolver
viewResolver.setViewClass(classOf[JstlView])
viewResolver.setPrefix("/WEB-INF/views/")
viewResolver.setSuffix(".jsp")
viewResolver
}
}
See this great writeup for more on Spring MVC Configuration.
To show a simple dependency this example includes a 'service' which provides the name to render in HTML.
package com.robb1e.helloworld
import org.springframework.stereotype.Service
trait Name {
def name: String
}
@Service
class NameService extends Name {
def name = "world"
}
The trait isn't strictly required, but enables me to introduce the comparison between Java Interfaces and how they are used in testing and Java Abstract classes in that they can be partially implemented.
The dependency of the Name gets injected into the controller using the autowired command in the class definition. The class has a constructor which requires a Name class and that's created and injected from the snippet above.
package com.robb1e.helloworld
import org.springframework.beans.factory.annotation.Autowired
import org.springframework.stereotype.Controller
import org.springframework.ui.Model
import org.springframework.web.bind.annotation.{RequestMapping, RequestMethod}
@Controller
@RequestMapping(Array("/"))
class HelloWorldController @Autowired() (nameService: Name) {
@RequestMapping(method = Array(RequestMethod.GET))
def index (model: Model) = {
model.addAttribute("name", nameService.name)
"index"
}
}
There's a lot going on here, let's break it down, starting with the package definition. The interesting thing with Scala is the package isn't dependent on the directory structure. In the example it is, but it doesn't need to be. Say good bye to those empty directories.
package com.robb1e.helloworld
We have to import a few classes, Autowired for the automatic injecting of dependencies; Controller to declare what type of class this is, Model to hold the variables to be passed down to the view. The last line includes two imports in one line, RequestMapping and RequestMethod for the path and HTTP method being used. In Java you'd need to import these classes separately or have a wildcard import.
import org.springframework.beans.factory.annotation.Autowired
import org.springframework.stereotype.Controller
import org.springframework.ui.Model
import org.springframework.web.bind.annotation.{RequestMapping, RequestMethod}
Here we declare that this class is a controller and it listens to the path '/'. We also declare it to be autowired and define the Name dependency.
@Controller
@RequestMapping(Array("/"))
class HelloWorldController @Autowired() (nameService: Name) {
Now we map our method to the HTTP method that comes through on the path this class is listening too. We receive the model and add our name to it so that it's used in the view.
@RequestMapping(method = Array(RequestMethod.GET))
def index (model: Model) = {
model.addAttribute("name", nameService.name)
"index"
}
}
Finally we have a simple JSP which uses the name variable passed into it from the controller which it's dependency injected into it.
<h1>Hello, ${name}</h1>
If you've followed this through, you've just got a glimpse of what Scala can provide, and how it can work with your existing tools.