Using XML processing typically simplifies a developer’s job–but not when you’re programming in c++. Ever wish someone would create the C++ equivalent of XMLBeans? Someone has. Find out how this new open-source tool fills a serious gap in the C++ software environment.
You May Also Like
Integration tests with Maven and JUnit
- byRafał Nowak
- August 10, 2013
Validation with warnings in scala with scalaz
- byAjk
- August 26, 2014
Grails render as JSON catch
- byTomasz Kalkosiński
- November 21, 2012
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