Over a million developers have joined DZone.

OCI and DZone Present Grails Quickcast #5: Retrieving Runtime Config Values In Grails 3

DZone's Guide to

OCI and DZone Present Grails Quickcast #5: Retrieving Runtime Config Values In Grails 3

DZone is proud to partner with Object Computing, Inc. to bring you the Grails Quickcast series. In this Quickcast, you'll learn about the pros and cons of techniques for retrieving configuration values at runtime.

· Java Zone ·
Free Resource

Get the Edge with a Professional Java IDE. 30-day free trial.

Today we bring you a new Grails Quickcast, where Grails co-founder Jeff Scott Brown highlights some of the great features of the Grails framework.  In less than 18 minutes, Jeff describes several techniques for retrieving configuration values at runtime and discusses the pros and cons of these different techniques. The Grails Quickcast series is brought to you from OCI and DZone.  

Grails leverages the “Convention Over Configuration” design paradigm, which functions to decrease the number of decisions that a developer using the framework is required to make without losing flexibility. This is one of the main reasons why Grails significantly increases developer productivity!

While Grails applications often involve considerably less configuration than similar applications built with other frameworks, some configuration may still be necessary. In this short video, Jeff shares a number of mechanisms that make it easy for Grails developers to define configuration values and to gain access to those configuration values at runtime.  

For this Quickcast, you’ll need no more than a basic understanding of Grails:

Grails 3 - Reading Config Values Quickcast from OCI on Vimeo.

See an accompanying article on the OCI Grails Team Blog at http://grailsblog.ociweb.com/posts/2016/08/31/retrieving-config-values.html.

Get the Java IDE that understands code & makes developing enjoyable. Level up your code with IntelliJ IDEA. Download the free trial.

grails ,runtime ,design patterns

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}