When comparing Play 2 vs CaptainCasa Enterprise Client, 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 CaptainCasa Enterprise Client is ranked 6th.
Specs
Ranked in these QuestionsQuestion 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 clustering
Pro Very fast dialogs
Very fast even with many controls. CaptainCasa Enterprise client is much faster than Vaadin when writting similar programs.
Pro Fast and powerful
Pro Longlife framework
Pro CDI via EL
Separation of the backend code and the creation of the pages / Injection of the code (CDI) into the pages via expression language (EL).
Pro High security
Pro Server development with Java
No javascript is needed, everything is developed on the server with Java. Optimized roundtrip.
Pro Free use
Pro Good scalability
In addition to the extremely good performance, which already ensures that the system can be scaled well, clustering of the system is already provided for in the software architecture.
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
