Voting

why am I writing this in XML insaetd of Java i believe you missed the all point IoC. IoC isn't going make developer's life easy, but it's going create application that are  configurable  without any modifications of the code. That's the idea. If i rename a class : Well you don't. You don't use IoC inside your own POJOs or in your own package. You use IoC on more  component  scale.I tried to make a concrete example :Your application used a DAO pattern, and your implementation used an Oracle DB. You have a new client but he wish that you use is db : MySQL.Using IoC garantee you that once you have develop this new implementation, and test it as a standalone (this is another very important aspect of IoC), you application will be easily swithc to this new implementation.Finally, don't forget that IoC comes with Micro kernel, wich means that your gain the advantage of a reconfigurable application without the  heavyness  of EJB for instance To conclude:*IoC between component not classes !*Easy deploy and easy changing of configuration*Test Units*lightness of microkernelI believe i didn't miss a major feature Final note : IoC is an architectural pattern not a design pattern, IoC describes how to built a apps not a class