[danielatc]

I think you need to reconsider your views regarding play. Version 2.0 has been a major improvement regarding a lot of issues. Asynchronous Requests are inbuilt as well as Websockets. (And Json serialization is as easy as Json.toJson()) I agree that static controllers are not always ideal considering that Java does not support inheritance of static methods, but the arguments of why static controllers are chosen can be found here: http://stackoverflow.com/a/5193721/616974

Still I think that developing with the play framework is a very productive process and can be compared with the likes of ror/django etc with the benefits of type safety all the way (including the templates)

[latch]

I did look at 2.0 when it came out, and I'm under the impression that you still need to write a custom binder. Just now I tried to look it up, but the documentation points to:

http://www.playframework.org/documentation/2.0/JavaJson

which is a 404.

I also don't see a nice way to respond with the appropriate format based on the accept-header...not that you can't write that yourself.

[Ygg3]

How did you get that link? Here is what I get when I browse documentation.

http://www.playframework.org/documentation/2.0.1/JavaJsonReq...

[latch]

http://www.playframework.org/documentation/2.0/JavaRouting

http://www.playframework.org/documentation/2.0/JavaXmlReques...

it's all over the place...search for "working with json" on those pages. Thanks for the correct link though.

[danielatc]

Here the version of the documentation from the git repository: https://github.com/playframework/Play20/wiki/Javajson

it states that the jackson library ( http://jackson.codehaus.org/ ) is included in the framework which allows for type safe json bindings