-
Notifications
You must be signed in to change notification settings - Fork 5
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
Do the @ComponentScan on ApplicationContext#start #27
Comments
damjangelovski
added a commit
that referenced
this issue
Jul 25, 2016
- added ConfigurationUtil.isConfigurationClass - added logic for loading components and properties in ComponentData - added PropertySourceUtil - adjusted existing tests accordingly [work-in-progress] [reviewed by @saskodh and @draganAndonovski]
Merged
damjangelovski
added a commit
to saskodh/framework-showcase
that referenced
this issue
Jul 25, 2016
- Feature provided within this issue saskodh/framework#27 [reviewed by @saskodh and @draganAndonovski]
Fix TODOs for adding missing unit tests in ComponentScanUtil |
damjangelovski
added a commit
that referenced
this issue
Jul 26, 2016
- added RequireUtils - fixed previosly added todos on the tests [reviewed by @saskodh]
damjangelovski
added a commit
that referenced
this issue
Jul 26, 2016
[#27] Do the @componentscan on ApplicationContext#start
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Currently the component scanning is implemented in the decorator and it runs immediately when the configuration class is loaded. We would like to replace that with lazy loading that is done when the configuration class is used to start an ApplicationContext.
Task
Make the @ComponentScan-ining lazy loading the components constructors on ApplicationContext startup. Make sure that other decorators used together with @componentscan work well with that. Example: @import, @propertysource..
Note: @propertysource should also lazy load the properties file. (Pass the file path instead of the actual file).
The text was updated successfully, but these errors were encountered: