Anyone using the Play framework

Anyone already familiar with the Play framework? I'm considering to rewrite my WebApp that has the standard JEE stack (Struts / Spring / Morphia / mongoDB) to a (Play / Scala / Morphia / mongoDB). I'm gaining quite a bit of experience with Scala in the last couple days, but haven't heard about the Play framework. I guess it is part of the typesafe stack and I'm considering it as a potential replacement for my Struts layer. Any pointers to some useful materials? Case studies? I know Google is my friend but in case if you could know of any trustworthy case studies, let me know!

I'm using Play 1.2.3 for one of my projects; but with Java not Scala.

Play 2 is useless to me as it would require a complete rewrite of the project (Play 2 is not backward compatible with Play 1), and Play 2 apps cannot deploy to a servlet container. Useless in production environments invested in Tomcat or any other servlet container.

P.S. Play would not replace just the Struts layer. It would replace all layers.

So does that make Lift a better choice for a Scala framework? The Lift website claims "you can still use your favorite Java libraries and deploy to your favorite Servlet Container and app server".

I have no experience with Lift and have only heard vague grumblings.

Bear Bibeault wrote:I have no experience with Lift and have only heard vague grumblings.

Darn - I was hoping for very specific grumblings...

Well, I can give you lots of those on a variety of subjects!

Just not Lift.

Bear Bibeault wrote:… Play 2 apps cannot deploy to a servlet container. Useless in production environments invested in Tomcat or any other servlet container.

Note that investment in Tomcat does not necessarily mean that nothing else may be used: not every HTTP resource has to run on the same kind of server, and not every organisation really insists on one-size-fits-all architecture. Besides, there was a time when Tomcat was the new thing.

Peter Hilton wrote:Note that investment in Tomcat does not necessarily mean that nothing else may be used: not every HTTP resource has to run on the same kind of server, and not every organisation really insists on one-size-fits-all architecture. Besides, there was a time when Tomcat was the new thing.

No argument from me, but this client would not consider deploying any other way.