On 3/13/06, Jubin Kuriakose <[EMAIL PROTECTED]> wrote: > But its growth is limited to being a webframework only. Spring on the other > hand is the whole deal.
That's a bit of a misnomer, really. The Spring distribution contains several interdependant frameworks. They have a Dependency Injection piece and a AOP piece and mock piece and MVC piece. Sure, Spring tosses in a Web MVC framework, and it's a nice piece of work, but it is separate and distinct from the core Spring dependency framework. If single-source solutions tickle your fancy, then sure, bundling is a benefit. But, if you are trying to put together a stable, best of breed solution, then you might not always be able to get what you want from a single vendor. The Spring DI framework is an excellent tool. I use it every day, both for Java and for .NET. In WebWork/Action2, the Spring integration is better than ever. But, the Spring Core and Spring MVC are distinct animals. -- HTH, Ted. ** http://www.husted.com/ted/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
