New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bean property overrides not working on app startup #9133

Closed
pledbrook opened this Issue Jul 26, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@pledbrook
Member

pledbrook commented Jul 26, 2015

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.

@pledbrook pledbrook added the v3.x label Jul 26, 2015

@pledbrook

This comment has been minimized.

Show comment
Hide comment
@pledbrook

pledbrook Jul 26, 2015

Member

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.

Member

pledbrook commented Jul 26, 2015

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.

@graemerocher graemerocher added this to the grails-3.0.4 milestone Jul 27, 2015

graemerocher added a commit to grails/grails3-functional-tests that referenced this issue Jul 27, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment