Dependency Injection and Inversion Control(依赖注入和反向控制)

A Java application - a loose term that runs the gamut from constrained,embedded applications to n-tier,server-side enterprise applictions - typically consists of objects that collaborate to form the application proper.Thus the objects in an application have dependencies on each other.

一个Java应用程序不那么标准的解释:它运行的范围从受限制的嵌入式应用程序到n层服务器端企业级应用程序-典型的都由对象,适当的应用程序组成

因此对象在应用程序和彼此有依赖关系

Although the Java platform provides a wealth of application development functionality.it lacks the means to organize the basic building blocks into a coherent whole,leaving that task to architects and developer.Although you can use design patterns such as Factory,Abstract Factory,Builder,Decorator,and Service Locator to compose the various classes and object instances that make up an application,these patterns are simply that:best practices given a name,with a description of what the pattern does,where to apply it,the problems it address,and so forth.Patterns are formalized best practices that you must implement yourself in your application.

虽然Java平台提供大量的应用程序开发功能,它缺乏连贯完整的组织基础构建块的手段 把这个任务留给了架构师和开发人员.虽然你可以使用设计模式比如:工厂,抽象工厂,建造者,装饰和服务定位器去把各种各样的类和对象 实例组成构成一个应用程序.这些模式是简单的这:最佳实践描述模式所做的事,在哪里应用它,它解决的问题...等等给予一个名字,模式是正式的最佳实践这你必须实现你自己的模式在你的应用程序.

The Spring Framework Inversion of Control(IoC) component address this concern by providing a formalized means of composing disparate components into a fully working application ready for use.The Spring Framework in this manner to engineer robust,maintainable applications.

Spring框架反向组件提供一个正式的手段去组成部件到充分工作的应用程序(完整的应用程序)解决了这个问题准备好使用Spring框架建造健壮,可维护的应用程序在这种方式下.

Background

"This question is,what aspect of control are[they] inverting?"Martin Fowler posed this question about Inversion of Control(IoC) on this site in 2004.Fowler suggested renaming the principle to make it more self-explanatory and came up with Dependency Injection.

背景

"这个问题是在什么方面控制[他们]反向?"关于反向控制在2004年在这个网站Martin Fowler提出了这个问题.Fowler建议重命名原则使其更加不言自明以及提出了依赖注入.