- Play Framework Cookbook
- Table of Contents
- Play Framework Cookbook
- Credits
- Foreword
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Basics of the Play Framework
- Introduction
- Downloading and installing the Play framework
- Creating a new application
- Defining routes as the entry point to your application
- Configuring your application via application.conf
- Defining your own controllers
- Defining your own models
- Using fixtures to provide initial data
- Defining your own views
- Writing your own tags
- Using Java Extensions to format data in your views
- Adding modules to extend your application
- Using Oracle or other databases with Play
- Understanding suspendable requests
- Understanding session management
- 2. Using Controllers
- Introduction
- URL routing using annotation-based configuration
- Basics of caching
- Using HTTP digest authentication
- Generating PDFs in your controllers
- Binding objects using custom binders
- Validating objects using annotations
- Adding annotation-based right checks to your controller
- Rendering JSON output
- Writing your own renderRSS method as controller output
- 3. Leveraging Modules
- 4. Creating and Using APIs
- 5. Introduction to Writing Modules
- Introduction
- Creating and using your own module
- Building a flexible registration module
- Understanding events
- Managing module dependencies
- Using the same model for different applications
- Understanding bytecode enhancement
- Adding private module repositories
- Preprocessing content by integrating stylus
- Integrating Dojo by adding command line options
- 6. Practical Module Examples
- 7. Running in Production
- Introduction
- Test automation with Jenkins
- Test automation with Calimoucho
- Creating a distributed configuration service
- Running jobs in a distributed environment
- Running one Play instance for several hosts
- Forcing SSL for chosen controllers
- Implementing own monitoring points
- Configuring log4j for log rotation
- Integrating with Icinga
- Integrating with Munin
- Setting up the Apache web server with Play
- Setting up the Nginx web server with Play
- Setting up the Lighttpd web server with Play
- Multi-node deployment introduction
- A. Further Information About the Play Framework
- Index
Alexander Reelsen is a software engineer living in Munich, Germany, where he has been working on different software systems, for example, a touristic booking engine, a campaign management and messaging platform, and a b2b ecommerce portal. He has been using the Play framework since 2009 and was immediately astonished by the sheer simplicity of this framework, while still being pure Java. His other interests includes scaling shared-nothing web architectures and NoSQL databases.
Being a system engineer most of the time, when he started playing around with Linux at the age of 14, Alexander got to know software engineering during studies and decided that web applications are more interesting than system administration.
If not hacking in front of his notebook, he enjoys playing a good game of basketball or streetball.
Sometimes he even tweets at http://twitter.com/spinscale and can be reached anytime at <[email protected]>.
If I do not thank my girlfriend for letting me spend more time with the laptop than with her while writing this book, I fear unknown consequences. So, thanks Christine!
Uncountable appreciation goes out to my parents for letting me spent days and (possibly not knowing) nights in front of the PC, and to my brother Stefan, who introduced me into the world of IT - which worked pretty well until now.
Thanks for the inspiration, fun, and fellowship to all my current and former colleagues, mainly of course to the developers. They always open up views and opinions to make developing enjoyable.
Many thanks go out to the Play framework developers and especially Guillaume, but also to the other core developers. Additionally, thanks to all of the people on the mailing list providing good answers to many questions and all the people working on tickets and helping to debug issues I had while writing this book.
My last appreciation goes to everyone at Packt Publishing, who was involved in this book.
-
No Comment