revised section on inheriting annotations from interfaces

git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@2608 50f2f4bb-b051-0410-bef5-90022cba6387

spring-framework-reference/src/transaction.xml

@@ -1416,9 +1416,7 @@ public class DefaultFooService implements FooService {
       <interfacename>@Transactional</interfacename> annotation is not enough
       to activate the transactional behavior. The
       <interfacename>@Transactional</interfacename> annotation is simply
-      metadata that can be consumed by something<!--Please identify *something* . 
+      metadata that can be consumed by some runtime infrastructure that is
-TR: OK AS IS.it's not defined what this something is. could be code written by the user or could be an 
-existing BeanPostProcessor provided or something else--> that is
       <interfacename>@Transactional</interfacename>-aware and that can use the
       metadata to configure the appropriate beans with transactional behavior.
       In the preceding example, the
@@ -1433,8 +1431,8 @@ existing BeanPostProcessor provided or something else--> that is
           <interfacename>@Transactional</interfacename> annotation on an
           interface (or an interface method), but this works only as you would
           expect it to if you are using interface-based proxies. The fact that
-          annotations are <emphasis>not inherited</emphasis> means that if you
+          Java annotations are <emphasis>not inherited from interfaces</emphasis>
-          are using class-based proxies
+          means that if you are using class-based proxies
           (<literal>proxy-target-class="true"</literal>) or the weaving-based
           aspect (<literal>mode="aspectj"</literal>), then the transaction
           settings are not recognized by the proxying and weaving