Play 2.1.1 released

[James Roper]

The Play team is pleased to announce the release of Play 2.1.1!

This is primarily a bugfix release.  Most notably fixed in this release:

• Reverted changes to multipart/form-data API so that no file submitted can be easily detected
  
• Reverse router now escapes String path parameters
  
• Invalid escape combinations in the query string and path now return 400 errors
  
• Routes files that only contain includes now compile
  
• Javadoc generation is now working
  
• Compiled assets are no longer part of watched sources
  
• Fixed some compilation problems on Windows
  
• Improved routes helpers implementation
• #884 Play can once again handle file uploads greater than 2GB (this was a regression in Netty, fixed by upgrading to 3.6.3) 
• #889 Performance/concurrency bottleneck fix for JSON serialisation in Scala
• #888 Fix Javascript reverse router default values
• JSON macro fixes and improvements

To upgrade from Play 2.1.0, simply download and extract Play 2.1.1, and then update the Play SBT plugin version in project/plugins.sbt to 2.1.1.

Play 2.1.1 can be downloaded here:

http://downloads.typesafe.com/play/2.1.1/play-2.1.1.zip

Thankyou to all the community members that have contributed to this release to make it happen.

Enjoy!

James Roper

[Jason Pearson]

Hoorah! Great job!

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Pascal Voitot Dev]

great :D

finally no more JSON companion object question :D

James Roper

--

[azwar akbar]

Wunderbarrr.......!! :D

Love this point "Reverse router now escapes String path parameters"

Congratulation...

Thanks for PlayFramework team and also it's community.

--


regards,
Azwar Akbar

[Michael Slinn]

The zip file extracts fine under Windows, but under Ubuntu I get:

caution: filename not matched:  play\-2.1.1/framework/test/integrationtest/app/controllers/\?\?\?\?$7\?\?.java

Mike

[Michael Slinn]

BTW, the extraction works fine from a command line, but not when using the GUI (Archive Manager).

Mike

[Andrew Gaydenko]

API refs to src go to 404, say https://github.com/playframework/Play20/tree/2.1.1/framework/src/play/src/main/scala/play/api/mvc/Action.scala

[Hugo Cura]

Hello

Since upgrading I'm unable to run my application (that worked fine under 2.1.0 and 2.0.x).

I believe it has something to do with the netty upgrade and it happends where I'm creating my own Akka System (that I use for remoting).

Error: IllegalStateException: await*() in I/O thread causes a dead lock or sudden performance drop. Use addListener() instead or call await*() from a different thread.

Stacktrace:
Caused by: java.lang.IllegalStateException: await*() in I/O thread causes a dead lock or sudden performance drop. Use addListener() instead or call await*() from a different thread.
    at org.jboss.netty.channel.DefaultChannelFuture.checkDeadLock(DefaultChannelFuture.java:342) ~[netty-3.6.3.Final.jar:na]
    at org.jboss.netty.channel.DefaultChannelFuture.awaitUninterruptibly(DefaultChannelFuture.java:256) ~[netty-3.6.3.Final.jar:na]
    at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:269) ~[netty-3.6.3.Final.jar:na]
    at akka.remote.netty.NettyRemoteServer.start(Server.scala:54) ~[akka-remote_2.10-2.1.0.jar:na]
    at akka.remote.netty.NettyRemoteTransport.start(NettyRemoteSupport.scala:179) ~[akka-remote_2.10-2.1.0.jar:na]
    at akka.remote.RemoteActorRefProvider.init(RemoteActorRefProvider.scala:87) ~[akka-remote_2.10-2.1.0.jar:na]
    at akka.actor.ActorSystemImpl._start$lzycompute(ActorSystem.scala:584) ~[akka-actor_2.10-2.1.0.jar:na]
    at akka.actor.ActorSystemImpl._start(ActorSystem.scala:582) ~[akka-actor_2.10-2.1.0.jar:na]
    at akka.actor.ActorSystemImpl.start(ActorSystem.scala:591) ~[akka-actor_2.10-2.1.0.jar:na]
    at akka.actor.ActorSystem$.apply(ActorSystem.scala:111) ~[akka-actor_2.10-2.1.0.jar:na]
    at akka.actor.ActorSystem$.apply(ActorSystem.scala:104) ~[akka-actor_2.10-2.1.0.jar:na]
    at akka.actor.ActorSystem$.create(ActorSystem.scala:66) ~[akka-actor_2.10-2.1.0.jar:na]
    at akka.actor.ActorSystem.create(ActorSystem.scala) ~[akka-actor_2.10-2.1.0.jar:na]
    at communication.AkkaSystem.getSystem(AkkaSystem.java:16) ~[na:na]

communication.AkkaSystem.getSystem is where the system is created with:

ActorSystem.create(NAME, ConfigFactory.load().getConfig(NAME));

NAME = system name with matching configuration properties in application.conf.

Any ideas?

[James Ward]

I tried that on my Arch Linux system and it worked fine. So I'm not
sure if this indicates a bug in the zip or a bug in Ubuntu.

[Rich Dougherty]

Does this look like the same issue?

https://github.com/playframework/Play20/issues/839

The problem is caused by the fact that Netty doesn't like to be started from within a Netty worker thread, but in dev mode the application is often reloaded from within such a worker thread. The fix is simple, but in the meantime you might be able to work around the problem by starting your actor system in another thread.

Cheers

Rich

[Pere Villega]

Thanks for the great job guys :)

[James Roper]

On Thu, Apr 4, 2013 at 2:19 AM, Andrew Gaydenko <andrew....@gmail.com> wrote:

API refs to src go to 404, say https://github.com/playframework/Play20/tree/2.1.1/framework/src/play/src/main/scala/play/api/mvc/Action.scala

git push --tags

I forget it every time.... it's fixed now.

 

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
James Roper
Software Engineer

Typesafe - The software stack for applications that scale
Twitter: @jroper

[uud ashr]

Cool

[Hugo Cura]

Rich,

Thanks for the clear explanation. And yes, looks like it's the same.

For now I'll stay with the 2.1.0 as there's nothing big for me that needs updating.

I recall that I ended up using a separate akka system for remoting back in 2.0.x due to some netty+akka issue but I'm not sure what it was.

Hugo

[Rich Dougherty]

Also: I've nearly got a PR ready for this, so you should expect a fix in 2.1.2.

Cheers

Rich

--

[Irmo Manie]

git push --tags

I forget it every time.... it's fixed now.

#protip: https://github.com/sbt/sbt-release 

If you forget, you automate ;-)

[Vlad Vlaskin]

That would be great, waiting for 2.1.2 milestone.

Our team is trying to migrate  from Spring to Play!.

Thanks.

- Vlad 

[Guan]

Great job! Waiting for homebrew update ;)

[Alban Dericbourg]

I'd say a bug in Archive Manager since I did not get any issue on my (up to date) Arch Linux and the Ubuntu (12.10) at work using Ark.

[Željko Trogrlić]

Did you also fixed something in logging? In 2.1.0 I couldn't get custom configuration to work, but it works fine in 2.1.1

[Skamander]

Thanks for the release. Keep up the good work. :)

[Leon Derks]

Hi Jason,

Thanks for the new release: 

I just tried this new release, but my app doesn't work any more.

I am calling my api GET /api/profiles/:key  like this: /api/partOne:PartTwo.

But with 2.1.1 the key is null in my Controller. In 2.1.0 this was working. 

Is the : not allowed in 2.1.1? If so, what is the reason?

regards,

Leon

[Alex Jarvis]

Hi James,

Thanks for all the hard work. The release broke one of my tests because I was validating an identifier from the URI using the string ":id" as an example of something that fails, but it looks like Play picks this up before my code, returning the following in the response body:

Expected scheme name at index 0: :id

I fixed the test by using "id" without the colon as an example of a bad identifier for my application, but I was just wondering where the new URI validation rules are specified in the Play source, or even documented so that I can check through them.

Thanks,

Alex

On Wednesday, 3 April 2013 14:14:53 UTC+1, James Roper wrote:

[James Roper]

This is this problem:

https://github.com/playframework/Play20/pull/978

--

You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.