boyarsky (67) [Avatar] Offline
#1
page 27/28 - I think the non-DI way is unfairly represented. Having separate classes for Dev/QA/Prod was poor practice in the before DI was popular too. The best practice approach was to use property files or some externalization technique. But then the book says with Spring "with only a different configuration file for each environment." Yes, Spring does this. And it injects the values rather than making the code read the file. But implying we had separate code before and now we just have a file is misleading.
martijn.verburg (86) [Avatar] Offline
#2
Re: property files before DI
Hi Jeanne,

This is a fair observation, I will need to think of a more appropriate example. Again this is something that will be likely to be changed a little further down the track.

Cheers,
Martijn