#903 ✓wontfix
Kjetil Iversen

Reduce required boilerplate for await/continuations with annotations

Reported by Kjetil Iversen | June 10th, 2011 @ 08:05 AM

It would be cool to annotate a local variable in your controller method with e.g. @Await (or another suitable name) and the runtime would automatically wrap the method call in a Future and use await()


class MyController {
  public static void action(){
    @Await String result = service.slowOperation("666");

class Service {
  public String slowOperation(String param){...}

Comments and changes to this ticket

  • Morten Kjetland

    Morten Kjetland June 10th, 2011 @ 10:25 AM

    • Tag set to await continuations
    • Assigned user set to “Morten Kjetland”

    For this to work it would have to automatically change it into this:

    String result = await(new Job<String>(){
      public String doJobWithResult() {
        return service.slowOperation("666");

    But there are some problems... if slowOperation where to take arguments, those args would have to be defined with final..

    Maybe it would be possible to give some useful error when enhancing the code..

    I'm not sure this is a good solution.

    maybe it is better to annotate the slowOperation-method instead

  • Morten Kjetland

    Morten Kjetland January 27th, 2012 @ 12:08 PM

    • State changed from “new” to “wontfix”

    as we're moving to 2.0, this is not going to be implemented

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Referenced by