I second that. As javaists are concerned, Play 2.x is not a good thing : bigger, slower, more rigid and with a lot scala dependencies/idioms you don't care abou

I second that. As javaists are concerned, Play 2.x is not a good thing : bigger, slower, more rigid and with a lot scala dependencies/idioms you don't care about. Forking Play 1.2.x could be a solution (and maybe remove the python console. After all that's a java framework) Or. Or one may use the extensibility of Play 2.x to remove the scala parts javaists don't want. It shouldn't too hard. Here's a thread on the official forum about it : https://groups.google.com/forum/?fromgroups=#!topic/play-framework/-BxpVFgyrgY https://groups.google.com/forum/?fromgroups=#!topic/play-fra...