To those who loves playframework v1.x but not feeling good with Play2,
I've provided a better choice:
ActFramework. And today I got the first version released to maven central repository.
Common features with PlayFramework v1.x
* The MVC architecture. Not component based
* Stateless/Share-nothing archtecture. The session implementation is borrowed from Play
* Hot reload on Dev mode
* Bytecode enhancement, which brings some nice features, e.g. the render(x, y, z) call automatically put the variable value into render argument linked to the variable name
* Controller action method parameter binding. Both support basic types and POJO, File etc
* Route configuration syntax
* Job support
What is different from PlayFramework v1.x
* No limits on controller method signature: `public static void`
* The app project is organized in standard maven structure, instead of a self-defined structure; also the module dependency is managed by maven
* Follow common standard, e.g. Dependency Injection, Bean Validation, i18n message bundle etc
* The built-in template engine is Rythm (
http://rythmengine.org). Which brings clear syntax and better performance over Play's groovy template engine
* Support define route mapping via annotation (like Spring and Jersey)
* Support CLI
* Much simpler yet powerful Job support
* Support event dispatching
* Performance is overall better than play1
The official website (
http://actframework.org) has detail information about features, documentation and video clips.
Enjoy!
Green