Skip to content
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

Chain Spring contexts of core and web #71

Open
rwi opened this issue May 4, 2019 · 0 comments
Open

Chain Spring contexts of core and web #71

rwi opened this issue May 4, 2019 · 0 comments
Assignees
Labels
enhancement technical classifies issues to be more technical, with effects more likely targeting devs and not end-users

Comments

@rwi
Copy link
Member

rwi commented May 4, 2019

Currently there are 2 separate Spring contexts, one for the core/backend beans (e.g. managers and services) and the other for the web frontend. The beans of the latter need to use a service locator to access their core bean dependencies. This should be changed so that the core Spring context becomes the parent of the web context which would allow us to use Spring DI to inject the core dependencies into the beans of the web frontend.

The technical challenging part is the web installer. It consists of a set of beans which also belongs to the web Spring context but can't be chained with the core context because the core context doesn't exist until the user completed some of the steps of the web installer.

@rwi rwi added enhancement technical classifies issues to be more technical, with effects more likely targeting devs and not end-users labels May 4, 2019
@rwi rwi self-assigned this May 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement technical classifies issues to be more technical, with effects more likely targeting devs and not end-users
Projects
None yet
Development

No branches or pull requests

1 participant