I both get your point and have to agree with a bunch of arguments in here, especially talking about rebuilding/redeploying .war files instead of "just" changing configuration. But after all, aren't we software developers, capable of doing jobs more difficult than "just" to wisely decide which tool to use and how much to make use of it? There probably are things that belong to some sort of configuration file, and there are some things that belong to code rather than configuration, I'd say. Spring+AOP+XML configuration is an incredibly powerful tool helping to keep code clean and yet keep track of how things work together... given one does it right. But in my opinion that is the very point: We should consciously decide which tool to be used for which solution, rather than blindly rely upon a "one-size-fits-all" approach. And, for that matters... Maybe we just have to make better solutions... What sort of approach instead of XML configuration would you prefer here, given not to have to mess with your code each time, say, you add/remove some AOP'ish service to it?
Cheers,
Kristian
↧