Note: The slides will be synchronous to the Tutorials at tech-phile.com
for Play Framework.
Introduction : Why Play?
Built in testing tools
Built on Akka
RESTful by default
Play Framework : Layout I
→ Application sources
→ Compiled asset sources
→ Typically LESS CSS sources
→ Typically CoffeeScript sources
→ Application controllers
→ Application business layer
→ Application build script
→ Configurations files and other non-compiled resources (on
→ Main configuration file
→ Routes definition
Play Framework : Layout II
→ Public assets
→ CSS files
→ Image files
→ sbt configuration files
→ Marker for sbt project
→ sbt plugins including the declaration for Play itself
→ Unmanaged libraries dependencies
→ Standard logs folder
→ Default log file
→ Generated stuff
→ Compiled class files
└ classes_managed → Managed class files (templates, ...)
└ resource_managed → Managed resources (less, ...)
→ Generated sources (templates, ...)
→ source folder for unit or functional tests
Contains all executable artifacts: Java/Scala Source Code
Templates (views package)
Compiled assets sources(CoffeeScript, LESS etc) : app/assets
Three standard packages in the app directory
Own packages can be added.
The directory is split into three standard sub-directories for images, CSS
Contains the application’s configuration files.
Two main files are:
application.conf -> the main configuration file for the application, which
contains standard configuration parameters.
routes -> the routes definition file.
lib/ , project/ Directory
lib/ : all JAR files you want to manually manage outside the build system.
project/ : plugins.sbt defines sbt plugins used by this