From 377359b924b0bca8a67d6238b01f5c24e8c25efa Mon Sep 17 00:00:00 2001 From: Thomas Risberg Date: Wed, 9 Sep 2009 17:28:34 +0000 Subject: [PATCH] polished --- spring-framework-reference/src/orm.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/spring-framework-reference/src/orm.xml b/spring-framework-reference/src/orm.xml index 1af6ae3ae1..ace62bbf63 100644 --- a/spring-framework-reference/src/orm.xml +++ b/spring-framework-reference/src/orm.xml @@ -17,12 +17,12 @@ Dependency Injection. 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 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; however, coverage of this style can be found in the Appendix. + linkend="classic-spring-orm" /> in the appendices. Spring adds significant enhancements to the ORM layer of your choice 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 Furthermore, transaction semantics like propagation behavior and isolation level can be changed in a configuration file and do not affect - the business service implementations. + the business service implementations. The following example shows how you can configure an AOP transaction interceptor, using XML, for a simple service class: