What
Is Play Framework?
Play was created in May 2007 by software developer Guillaume Bort, while working at Zengularity SA (formerly known as Zenexity). Play is heavily inspired by ASP.NET MVC, Ruby on Rails and Django.
Play Framework is an open-source, type-safe
reactive platform, and high-productivity written in Scala and Java. Play
Framework is used to build scalable, fast, and real-time
web applications with Java and Scala.
Play was created in May 2007 by software developer Guillaume Bort, while working at Zengularity SA (formerly known as Zenexity). Play is heavily inspired by ASP.NET MVC, Ruby on Rails and Django.
Now Play 2 is fully RESTful - there is no Java EE
session per connection. It is also supports to JUnit and Selenium for
unit testing.
Is
Play Framework open-source?
Yes! Play Framework is an open-source and
Licensed under the Apache License, Version 2.0.
What
Is The Advantage Of Play Framework?
The list of Advantage of Play Framework is -
1. Open
Source
2. Fully
RESTful framework
3. Modern
stacks
4. Java
and Scala
5. Amazing
error handling
6. Reactive
7. Supported
8. Flexible
9. Graphically
improved developer productivity
10. A
full embedded testing framework and an automatic file uploads functionality
Is
Play Framework follows MVC pattern?
Yes! Play Framework follows MVC
(model–view–controller) architectural pattern.
Which
is the latest version?
The latest version of Play Framework is - 2.6.20
What’s
new in Play 2.6?
1. Scala
2.12 support
2. Injectable
Twirl Templates
3. Added
gzip filter
4. Just
as in Scala, Play now has components to enable Java Compile Time Dependency
Injection.
5. Play
now uses JSON Web Token (JWT) format for session and flash cookies
6. SLF4J
Marker support has been added to play.Logger and play.api.Logger
7. Play’s
support for futures in asynchronous operations has been improved, using the
Futures trait.
8. Updated
Templates with Preconfigured CustomExecutionContexts
9. Filters
Enhancements
10. Testing
Improvements
11. Play
JSON improvements
12. File
Upload Improvements
How
to migrate?
The following steps need to be taken to update -
1. Play
upgrade
2. Sbt
upgrade to 0.13.15
3. Guice
DI support moved to separate module
4. OpenID
support moved to separate module
5. Play
JSON moved to separate project
6. Play
Iterates moved to separate project
|
Hi there! Welcome to my blog. My name is Anil Singh. I'm a author of this blog.
For more detail about me, kindly refer to this link..
|
You Might Also Like
