OCI and DZone Present: A Grails Quickcast #2: JSON Views
OCI and DZone Present: A Grails Quickcast #2: JSON Views
DZone is proud to partner with Object Computing, Inc. to launch a new series: the Grails Quickcasts, led by Jeff Brown, principal software engineer and Grails practice lead at OCI, and senior member of the Core Grails Team. Wet your whistle in this intro to JSON views!
Join the DZone community and get the full member experience.
Join For FreeDiscover how you can get APIs and microservices to work at true enterprise scale.
Grails co-founder Jeff Scott Brown continues his deep dives into Grails with another awesome Grails Quickcast, brought to you by DZone in collaboration with OCI. In case you missed part 1, here's a dive into interceptors.
Grails co-founder Jeff Scott Brown continues his dives into Grails with another awesome Quickcast. In a delightful and informative 15 minutes, Brown probes JSON views. Beginning with a Grails 3.1.1 application, created with a standard web profile, Brown added a few custom domain classes. The artist class has albums associated with it, and is annotated with grails.rest.Resource.
The ultimate goal is publishing a REST API under /artists for managing instances of the artist class, and to support the JSON and XML formats.
Brown uses music examples, including Space Oddity by David Bowie (RIP), and Close to the Edge by Yes. Sending a request to /artists gives a list of artists all of whom have albums associated with them. While the app is running in development mode, the JSON files can be altered and the effects of those changes can be seen real-time in the application. For example, switching "ArtistName": "Riverside" to "theArtistName": "Riverside".
This Quickcast assumes basic knowledge of Grails, JSON, and REST APIs. Check out Brown’s neat intro to JSON views below!
APIs and microservices are maturing, quickly. Learn what it takes to manage modern APIs and microservices at enterprise scale.
Like This Article? Read More From DZone
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}