Asciidoc revision (chapter declarations, javadoc references, etc)

Author: jhoeller

Diff for: src/docs/asciidoc/core/core-aop-api.adoc

@@ -1,8 +1,6 @@
 [[aop-api]]
 = Spring AOP APIs
 
-
-
 The previous chapter described the Spring's support for AOP with
 @AspectJ and schema-based aspect definitions. In this chapter, we discuss the lower-level
 Spring AOP APIs and the AOP support typically used in Spring 1.2 applications. For new
@@ -14,6 +12,7 @@ in Spring 5.
 
 
 
+
 [[aop-api-pointcuts]]
 == Pointcut API in Spring
 
@@ -129,7 +128,6 @@ Spring provides several convenient pointcut implementations. You can use some of
 Others are intended to be subclassed in application-specific pointcuts.
 
 
-
 [[aop-api-pointcuts-static]]
 ==== Static Pointcuts
 
@@ -198,16 +196,13 @@ pointcut and advice, as the following example shows:
 
 You can use `RegexpMethodPointcutAdvisor` with any `Advice` type.
 
-
-
 [[aop-api-pointcuts-attribute-driven]]
 ===== Attribute-driven Pointcuts
 
 An important type of static pointcut is a metadata-driven pointcut. This uses the
 values of metadata attributes (typically, source-level metadata).
 
 
-
 [[aop-api-pointcuts-dynamic]]
 ==== Dynamic pointcuts
 
@@ -276,6 +271,7 @@ for example, "`all methods that change instance variables in the target object.`
 
 
 
+
 [[aop-api-advice]]
 == Advice API in Spring
 
@@ -366,7 +362,6 @@ are not currently interoperable between frameworks, and the AOP Alliance does no
 currently define pointcut interfaces.
 
 
-
 [[aop-api-advice-before]]
 ==== Before Advice
 
@@ -425,7 +420,6 @@ The following example shows a before advice in Spring, which counts all method i
 TIP: Before advice can be used with any pointcut.
 
 
-
 [[aop-api-advice-throws]]
 ==== Throws Advice
 
@@ -511,7 +505,6 @@ exception that is incompatible with the target method's signature!_
 TIP: Throws advice can be used with any pointcut.
 
 
-
 [[aop-api-advice-after-returning]]
 ==== After Returning Advice
 
@@ -562,7 +555,6 @@ thrown up the interceptor chain instead of the return value.
 TIP: After returning advice can be used with any pointcut.
 
 
-
 [[aop-api-advice-introduction]]
 ==== Introduction Advice
 
@@ -738,6 +730,8 @@ and stateful mixins.
 
 
 
+
+
 [[aop-api-advisor]]
 == The Advisor API in Spring
 
@@ -756,6 +750,7 @@ chain.
 
 
 
+
 [[aop-pfb]]
 == Using the `ProxyFactoryBean` to Create AOP Proxies
 
@@ -1085,6 +1080,7 @@ two global advisors:
 
 
 
+
 [[aop-concise-proxy]]
 == Concise Proxy Definitions
 
@@ -1164,6 +1160,7 @@ pre-instantiate it.
 
 
 
+
 [[aop-prog]]
 == Creating AOP Proxies Programmatically with the `ProxyFactory`
 
@@ -1205,6 +1202,7 @@ as you should in general.
 
 
 
+
 [[aop-api-advised]]
 == Manipulating Advised Objects
 
@@ -1298,6 +1296,7 @@ required.
 
 
 
+
 [[aop-autoproxy]]
 == Using the "auto-proxy" facility
 
@@ -1327,7 +1326,6 @@ This section covers the  auto-proxy creators provided by the
 `org.springframework.aop.framework.autoproxy` package.
 
 
-
 [[aop-api-autoproxy]]
 ==== `BeanNameAutoProxyCreator`
 
@@ -1435,6 +1433,7 @@ preceding example has a configurable order value. The default setting is unorder
 
 
 
+
 [[aop-targetsource]]
 == Using `TargetSource` Implementations
 
@@ -1552,7 +1551,7 @@ The following listig shows an example configuration:
 
 Note that the target object (`businessObjectTarget` in the preceding example) must be a
 prototype. This lets the `PoolingTargetSource` implementation create new instances
-of the target to grow the pool as necessary. See the {api-spring-framework}aop/target/AbstractPoolingTargetSource.html[Javadoc of
+of the target to grow the pool as necessary. See the {api-spring-framework}aop/target/AbstractPoolingTargetSource.html[javadoc of
 `AbstractPoolingTargetSource`] and the concrete subclass you wish to use for information
 about its properties. `maxSize` is the most basic and is always guaranteed to be present.
 
@@ -1661,6 +1660,7 @@ any case, since not unsetting it might result in problematic behavior. Spring's
 
 
 
+
 [[aop-extensibility]]
 == Defining New Advice Types
 
@@ -1674,5 +1674,5 @@ support for new custom advice types be added without changing the core framework
 The only constraint on a custom `Advice` type is that it must implement the
 `org.aopalliance.aop.Advice` marker interface.
 
-See the {api-spring-framework}/aop/framework/adapter/package-frame.html[`org.springframework.aop.framework.adapter` Javadoc] for further
-information.
+See the {api-spring-framework}/aop/framework/adapter/package-frame.html[`org.springframework.aop.framework.adapter`]
+javadoc for further information.