Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Play 2 vs Apache Wicket, the Slant community recommends Play 2 for most people. In the question“What are the best Java web frameworks?” Play 2 is ranked 4th while Apache Wicket is ranked 8th.
Question Ranking
Pros
Pro Very fast and easy to install, it is a revolutionary framework
Pro Great resources
With some basic starting tutorials and a fleshed out documentation, there will be no need to go asking others for help, there should be enough for a developer to find a solution.
Pro Asynchronous requests
Everything with Play has been built with asynchronous requests in mind. This will result in the application not blocking results while waiting on other operations. With this implemented your application can be developed with multiple threads in mind without worrying about hanging on one request before it completes another.
Pro Rapid application development
All error checking and testing done in the browser only needs a page refresh to show the latest updates. This is huge, allowing the ability to code in real-time and make quick edits. Without it the develop would need to reboot/recompile the entire application to test with new data.
Pro Supports Scala
Pro Easy way to create reusable panels or layouts
So it is easy to create, maintain or modify a consistent corporate design across all pages.
Pro Separation of code and layout
The HTML templates contain IDs that are references in Java code. There is no code in the templates.
Pro Valid links in template can be converted to valid links in output html
That way the IDE, e.g. IDEA can verify the links already in the templates and hence there are less bad links.
Pro No configuration mess
Nearly everything is handled in Java code.
Pro Human-friendly URLs
Cons
Con Not backword-compatible
Applications that have been written in Play 1 will not be supported in Play 2 as the core of the framework was rewritten in Scala. This includes plugins that were working in Play 1 as well.
Con Becoming a Scala framework
As Play continues to develop and mature it seems as if it is becoming less of a Java framework as the core has been rebuilt in Scala. This may deter adopters.
Con Steep learning curve
Con Newer versions might break existing code
