1 / 8

Introduction to Web Application Development using the Play Framework

Introduction to Web Application Development using the Play Framework. Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of Hawaii Honolulu HI 96822. About Web Application Development. Very important development area.

hiero
Download Presentation

Introduction to Web Application Development using the Play Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to Web Application Developmentusing the Play Framework Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of Hawaii Honolulu HI 96822

  2. About Web Application Development • Very important development area. • Every software engineer should know how! • Provides exposure to many interesting concepts: • "Model-View-Controller" architecture • "Three tier" architecture • Responsive UI design • Cloud-based deployment • Continuous integration • Scalability

  3. About Play Framework • Provides: • Simplicity, speed of RoR development • Type-safety through Java and Scala • Modern API by abandoning Servlets • High profile user: LinkedIn • They like the use of Scala and underlying libraries to provide scalability through non-blocking IO.

  4. Innovative features • Template (views) and route files are Scala classes • They compile!

  5. Initial issues • Development does not use Maven. • Play replaces Maven with its own build environment (Play console) based upon SBT (a Scala-based build tool). • What about QA (Checkstyle, PMD, FindBugs, Jacoco)? • No support "out of box". • We will add these back in after you get comfortable with Play

  6. Elements of Java Style violations(that we'll live with) • Public fields in model classes • Done to support automated database schema generation. • Static methods in controller classes • Play framework designers feel that instances create overhead without providing offsetting value. • Default package structure: model.*, view.*, controller.* • OK as long as packages will not be used outside of framework. • EJS Rule #1: Adhere to the style of the original.

  7. Elements of Java Style violations(that you need to fix) • "play new" creates sample classes with * imports • Fix this • Static methods in controller classes • Play framework designers feel that instances create overhead without providing offsetting value. • Default package structure: model.*, view.*, controller.* • OK as long as packages will not be used outside of framework. • EJS Rule #1: Adhere to the style of the original.

  8. Module structure • Introduction to the framework • MVC components: • Model development • View development • Controller development • Testing • Cloud-based deployment • Continuous Integration and QA

More Related