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