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

Remove BeanFactoryPostProcessor #102

Conversation

shochdoerfer
Copy link
Member

Injecting a container into a service is considered a bad practice, thus the BeanFactoryPostProcessor is removed. The general post processor logic is still in place, a custom BeanFactoryPostProcessor implementation can still be used.

Injecting a container into a service is considered a bad practice, thus the
BeanFactoryPostProcessor is removed. The general post processor logic is
still in place, a custom BeanFactoryPostProcessor implementation can still
be used.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 94.268% when pulling b15ea36 on shochdoerfer:feature/remove_beanfactory_postprocessor into ae5c04b on bitExpert:master.

@shochdoerfer shochdoerfer merged commit e5e449c into bitExpert:master Jun 15, 2017
@shochdoerfer shochdoerfer added this to the 0.9.0 milestone Jun 15, 2017
@shochdoerfer shochdoerfer deleted the feature/remove_beanfactory_postprocessor branch June 15, 2017 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants