You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm assuming that the bean property overrides mechanism is still supposed to work with Grails 3, but it definitely doesn't on startup. This renders a rather useful technique, configuration injection, dead. Interestingly, I noticed that configuration injection on controllers works after modifying the controller so it's reloaded.
I'll try to attach a bug report project, although I'm not sure how to do it in GitHub.
The text was updated successfully, but these errors were encountered:
Tested in Grails 3.0.3. I've put the bug report project on Dropbox. Simply unpack and do a run-app. I'm seeing it print out ">>>> null" because MyBeans name property is not being initialised from the value specified in application.groovy via bean property overrides.
I'm assuming that the bean property overrides mechanism is still supposed to work with Grails 3, but it definitely doesn't on startup. This renders a rather useful technique, configuration injection, dead. Interestingly, I noticed that configuration injection on controllers works after modifying the controller so it's reloaded.
I'll try to attach a bug report project, although I'm not sure how to do it in GitHub.
The text was updated successfully, but these errors were encountered: