polished
git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@1863 50f2f4bb-b051-0410-bef5-90022cba6387
This commit is contained in:
parent
d9f72a9ae3
commit
53bdd3e5f6
|
|
@ -17,12 +17,12 @@
|
||||||
Dependency Injection. <!--Identify *these support packages*. Do you mean Hibernate, JPA, etc? Is it correct to call them support packages?
|
Dependency Injection. <!--Identify *these support packages*. Do you mean Hibernate, JPA, etc? Is it correct to call them support packages?
|
||||||
TR: REVISED, PLS REVIEW. Changed to say features instead of packages. Reverted the "first-class support" sentence above since it is not
|
TR: REVISED, PLS REVIEW. Changed to say features instead of packages. Reverted the "first-class support" sentence above since it is not
|
||||||
IoC itself providing the support.-->They can participate in Spring's resource
|
IoC itself providing the support.-->They can participate in Spring's resource
|
||||||
and transaction management,and they comply with Spring's generic
|
and transaction management, and they comply with Spring's generic
|
||||||
transaction and DAO exception hierarchies. The recommended integration
|
transaction and DAO exception hierarchies. The recommended integration
|
||||||
style is to code DAOs against plain Hibernate, JPA, and JDO APIs. The
|
style is to code DAOs against plain Hibernate, JPA, and JDO APIs. The
|
||||||
older style of using Spring's DAO templates is no longer recommended;
|
older style of using Spring's DAO templates is no longer recommended;
|
||||||
however, coverage of this style can be found in the <xref
|
however, coverage of this style can be found in the <xref
|
||||||
linkend="classic-spring-orm" /> Appendix.</para>
|
linkend="classic-spring-orm" /> in the appendices.</para>
|
||||||
|
|
||||||
<para>Spring adds significant enhancements to the ORM layer of your choice
|
<para>Spring adds significant enhancements to the ORM layer of your choice
|
||||||
when you create data access applications. You can leverage as much of the
|
when you create data access applications. You can leverage as much of the
|
||||||
|
|
@ -407,7 +407,7 @@ TR: REVISED, PLS REVIEW.-->This declarative transaction capability allows you
|
||||||
|
|
||||||
<para>Furthermore, transaction semantics like propagation behavior and
|
<para>Furthermore, transaction semantics like propagation behavior and
|
||||||
isolation level can be changed in a configuration file and do not affect
|
isolation level can be changed in a configuration file and do not affect
|
||||||
the business service implementations. <!--give context to example; what is it showing, what is its purpose? TR: REVISED, PLS REVIEW. Added some context.--></para>
|
the business service implementations.<!--give context to example; what is it showing, what is its purpose? TR: REVISED, PLS REVIEW. Added some context.--></para>
|
||||||
|
|
||||||
<para>The following example shows how you can configure an AOP
|
<para>The following example shows how you can configure an AOP
|
||||||
transaction interceptor, using XML, for a simple service class:</para>
|
transaction interceptor, using XML, for a simple service class:</para>
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue