Question

Grails 1.3.7

I have some configuration located in an external config file. One of the entires looks like this:

site.maintenance.mode = false

I have a filter which checks for certain config settings for specific URLs. When I do a run-app or deploy a WAR into Tomcat and do:

boolean maintenanceMode = grailsApplication.config.site.maintenance.mode

maintenanceMode is coming back true. If I look at the config object in debug mode, this is what I get:

site={maintenance={mode=false, message="<p>Our trail guides are working hard to get the system back on track.</p><p>We're sorry, the account system is down for maintenance at the moment.  We'll get it back online as quickly as we can.  Thanks for your patience.</p>"}}

I have a controller that I use to reload this config file dynamically and hitting this controller will fix the issue. But I’m curious as to why it is incorrect on first runs and why the discrepency in what is getting put in the maintenanceMode variable vs what is actually in the config object.

Answer 1

Are you using a Java properties file or a Groovy file? If you’re using a properties file then I believe Grails will interpret site.maintenance.mode=false the same way as site.maintenance.mode='false' and since Groovy will interpret:

"false".asBoolean() == true

then that would explain why you would see that initial true value.

I just ran a simple test locally to verify this behavior. When I externalize my properties in a file called test.properties then site.maintenance.mode=false initially gets a boolean value of true, when I use a file called test.groovy then it interprets the boolean value of site.maintenance.mode=false as false. I believe this is because when you use a Groovy file Grails uses ConfigurationSlurper to process it but when you use a properties file Grails interprets everything as String name/value pairs.