Part I. Overview of Spring Framework
The Spring Framework is a lightweight solution and a potential one-stop-shop for building your
enterprise-ready applications. However, Spring is modular, allowing you to use only those parts that you
need, without having to bring in the rest. You can use the IoC container, with any web framework on
top, but you can also use only the Hibernate integration code or the JDBC abstraction layer. The Spring
Framework supports declarative transaction management, remote access to your logic through RMI or
web services, and various options for persisting your data. It offers a full-featured MVC framework, and
enables you to integrate AOP transparently into your software.
Spring is designed to be non-intrusive, meaning that your domain logic code generally has no
dependencies on the framework itself. In your integration layer (such as the data access layer), some
dependencies on the data access technology and the Spring libraries will exist. However, it should be
easy to isolate these dependencies from the rest of your code base.
This document is a reference guide to Spring Framework features. If you have any requests, comments,
or questions on this document, please post them on the user mailing list. Questions on the Framework
itself should be asked on StackOverflow (see https://spring.io/questions)
第一部分 spring框架概述
Spring框架是一种轻量级和有可能成为一站式的企业项目解决方案。但是,spring是组件化的,允许你只使用你需要的那一部分,其他部分可以不使用。你可以使用IoC容器和其他的web框架一起用,但是你也可以只使用hibernate集成代码或者jdbc抽象层。Spring支持声明式事务,通过RMI或者webService的远程调用和其他各种方式来保存你的数据。他提供了一个全功能MVC框架,可以透明地集成aop特性到你的软件中。
Spring被设计成不是侵入式,意味着你写的逻辑代码通常跟框架本身没有依赖,在你的整合层(比如数据库访问层),数据访问层和spring的库相关的依赖会存在。但是,它应该比较容易把这些依赖从你的其他基础代码分离出来。
这个文档是spring特性的参考手册。如果你对这个文档有什么请求,评论或者问题,请发送邮箱到用户邮箱列表中,spring框架的本身的问题应该去 StackOverflow询问,(访问https://spring.io/questions)