Menu
As in the title above, I am confused about pros cons between injecting applicationContext by directly @Autowired annnotation or implementing ApplicationContextAware interface in a singleton spring bean.
Which one do you prefer in which cases and why? Thanks.
256
The ApplicationContext interface extends an interface called MessageSource , and therefore provides internationalization (i18n) functionality.
ApplicationContext Implementation Classes Containers are as follows: AnnotationConfigApplicationContext container. AnnotationConfigWebApplicationContext. XmlWebApplicationContext.
The ApplicationContextAware Interface Spring provides an ApplicationContextAware interface that allows beans access to the ApplicationContext . This interface provides a single setApplicationContext method.
Actually, both are bad. Both of them tie your application to the Spring framework, thus inverting the whole inversion-of-control concept. In an ideal world, your application should not be aware of being managed by an ApplicationContext at all.
Once you have chosen to violate this principle, it doesn't really matter how you do it. ApplicationContextAware is the legacy version that has been around at least since Version 2.0. @Autowired is a newer mechanism but they work in pretty much the same way. I'd probably go with ApplicationContextAware, because it semantically makes clear what it is about.
199
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
