Play Framework 2.0 Final released
When I did a bit of Play 1.2 dev, I ran into two serious annoyances.<p>First, static actions make for untestable code. The only way to test this in 1.2 was to do full integration tests. You can't unit test controllers/actions, which to me is a horrible "opinion" to have. Looking at the docs, 2.0 [appears] to make an attempt via the callAction helper [1], but you still can't inject dependencies via a constructor and call instance methods. Static members in static languages make testing a real pain.<p>Second, JSON felt like a 2nd-class citizen. Dealing with JSON in either the request or the response felt barbaric. I don't see that they've improved things. Auto binding from a JSON request to an object should exist without having to write a bunch of custom JSON serializers...doubly so for outputting json.<p>[1] <a href="http://www.playframework.org/documentation/2.0/JavaFunctionalTest" rel="nofollow">http://www.playframework.org/documentation/2.0/JavaFunctiona...</a>