Bill Gorder wrote:No. The spring project is much more comprehensive then just a DI framework at this point. With the way that the specification trails years behind everything else by the time its realized it will just be missing something else imo.
I agree with Bill. One thing you can't easily do in
Java EE is run it from the command line. How many times I've seen people write data massaging utilities in Spring because JdbcTemplate is soo good (and much > 5 years old I may add) is one example. You also don't need to worry about profiles. And JavaConfig (though I'm still not a fan) will get rid of XML hell going forward.
If anything, I'm sure the Spring team will make sure Spring interoperates with Java EE's injection container, maybe even emulating or deferring part of itself to it, while still giving us factories for things that are tedious and slimming down ones that no longer are needed. To wit, we don't need to extend an abstract DAO class with Hibernate or JPA since they now give us the current session themselves, so Spring deprecated that.
I expect Spring to keep providing those big abstractions (integration, batch, Spring Data) for every area that isn't covered by a spec, and to interoperate with the ones that it doesn't need to provide anymore. And when they stop doing those things, then it will die. Which I assume will be a long time from now.