DDevelopment & Design

Tomek’s tray notes on Scrum

As Nigel Baker was giving his speach titled “10 tips that ScrumMasters should know, (but probably don’t!)” at Winter Agile Tuning, Tomasz Przybysz was taking notes on a paper tray. I’ve heard the talk was pretty good and a few people were trying to copy his tray. Since the original presentation is not yet available, I thought I’ll help with putting my own photo (phone quality) on-line. Maybe Tomek will take a while to put some insight into his notes? What say you, Tomasz? Click on the image to get the full (readable) size version.

Solution Architect @ TouK

— Previous article

4Developers 2010 Review

Next article —

GeeCON 2010

You May Also Like
DDevelopment & Design

Grails render as JSON catch

One of a reasons your controller doesn't render a proper response in JSON format might be wrong package name that you use. It is easy to overlook. Import are on top of a file, you look at your code and everything seems to be fine. Except response is still not in JSON format.

Consider this simple controller:

class RestJsonCatchController {
def grailsJson() {
render([first: 'foo', second: 5] as grails.converters.JSON)
    }

def netSfJson() {
render([first: 'foo', second: 5] as net.sf.json.JSON)
    }
}

And now, with finger crossed... We have a winner!

$ curl localhost:8080/example/restJsonCatch/grailsJson
{"first":"foo","second":5}
$ curl localhost:8080/example/restJsonCatch/netSfJson
{first=foo, second=5}

As you can see only grails.converters.JSON converts your response to JSON format. There is no such converter for net.sf.json.JSON, so Grails has no converter to apply and it renders Map normally.

Conclusion: always carefully look at your imports if you're working with JSON in Grails!

Edit: Burt suggested that this is a bug. I've submitted JIRA issue here: GRAILS-9622 render as class that is not a codec should throw exception