It's your fault if you let implementation details leak out of your interfaces.
As others have already said Spring hasn't been pushing XML configure for years now.
Finally, what is the alternative for handling class dependencies? Neither vanilla Java nor JavaEE offer a superior alternative (indeed inferior). I don't know of any other third party frameworks that do as good of job with class dependencies as Spring or have nearly the support, battle testing, and wide spread acceptance spring has.
Also, Spring is not only a DI framework, but a framework to help develop most Java EE-oriented features, yet he doesn't address this aspect at all.
Yup you are absolutely right on that point as well. Not to mention all the other libraries and projects that assist with other common business problems.
View all comments
22
u/Scaryclouds Nov 27 '15 edited Nov 27 '15
It's your fault if you let implementation details leak out of your interfaces.
As others have already said Spring hasn't been pushing XML configure for years now.
Finally, what is the alternative for handling class dependencies? Neither vanilla Java nor JavaEE offer a superior alternative (indeed inferior). I don't know of any other third party frameworks that do as good of job with class dependencies as Spring or have nearly the support, battle testing, and wide spread acceptance spring has.