Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Appendix refactoring

Browse Source 
1. Move schemas to local appendix within each top-level section.
2. Link to Javadoc for JSP tags
3. Purge Class Spring usage information

Issue: SPR-16045
This commit is contained in:
Rossen Stoyanchev
2017-10-05 07:23:18 -04:00
parent d04d4bfb4d
commit e5a5677fcd
11 changed files with 1831 additions and 3997 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/docs/asciidoc/core/core-aop.adoc
View File

@@ -259,9 +259,10 @@ element:
<aop:aspectj-autoproxy/>
----
This assumes that you are using schema support as described in <<appendix.adoc#xsd-configuration,
XML Schema-based configuration>>. See <<appendix.adoc#xsd-config-body-schemas-aop, the AOP schema>>
for how to import the tags in the `aop` namespace.
This assumes that you are using schema support as described in
<<core.adoc#xsd-schemas, XML Schema-based configuration>>. See
<<core.adoc#xsd-schemas-aop, the AOP schema>> for how to import the tags in the `aop`
namespace.
@@ -1553,9 +1554,9 @@ the new __syntax__ and refer the reader to the discussion in the previous sectio
of advice parameters.
To use the aop namespace tags described in this section, you need to import the
`spring-aop` schema as described in <<appendix.adoc#xsd-configuration,
`spring-aop` schema as described in <<core.adoc#xsd-schemas,
XML Schema-based configuration>>.
See <<appendix.adoc#xsd-config-body-schemas-aop, the AOP schema>>
See <<core.adoc#xsd-schemas-aop, the AOP schema>>
for how to import the tags in the `aop` namespace.
Within your Spring configurations, all aspect and advisor elements must be placed within
@@ -2793,8 +2794,9 @@ using Java based configuration simply add `@EnableSpringConfigured` to any
}
----
If you prefer XML based configuration, the Spring <<appendix.adoc#xsd-config-body-schemas-context,
`context` namespace>> defines a convenient `context:spring-configured` element:
If you prefer XML based configuration, the Spring
<<core.adoc#xsd-schemas-context, `context` namespace>>
defines a convenient `context:spring-configured` element:
[source,xml,indent=0]
[subs="verbatim,quotes"]

1376
src/docs/asciidoc/core/core-appendix.adoc Normal file
View File

File diff suppressed because it is too large Load Diff

9
src/docs/asciidoc/core/core-beans.adoc
View File

@@ -1711,7 +1711,8 @@ The above configuration is equivalent to the following Java code:
The p-namespace enables you to use the `bean` element's attributes, instead of nested
`<property/>` elements, to describe your property values and/or collaborating beans.
Spring supports extensible configuration formats <<appendix.adoc#xsd-configuration,with namespaces>>,
Spring supports extensible configuration formats
<<core.adoc#xsd-schemas,with namespaces>>,
which are based on an XML Schema definition. The `beans` configuration format discussed in this
chapter is defined in an XML Schema document. However, the p-namespace is not defined in
an XSD file and exists only in the core of Spring.
@@ -2771,7 +2772,7 @@ understand the "why" as well as the "how" behind it.
To create such a proxy, you insert a child `<aop:scoped-proxy/>` element into a scoped
bean definition (see <<beans-factory-scopes-other-injection-proxies>> and
<<appendix.adoc#xsd-configuration, XML Schema-based configuration>>).
<<core.adoc#xsd-schemas, XML Schema-based configuration>>).
Why do definitions of beans scoped at the `request`, `session` and custom-scope
levels require the `<aop:scoped-proxy/>` element?
Let's examine the following singleton bean definition and contrast it with
@@ -5293,7 +5294,9 @@ Or with an overridden value for the `proxyMode` as follows:
}
----
For further details, consult the <<appendix.adoc#annotation-programming-model,Spring Annotation Programming Model>>.
For further details, consult the
https://github.com/spring-projects/spring-framework/wiki/Spring-Annotation-Programming-Model[Spring Annotation Programming Model]
wiki page.
[[beans-scanning-autodetection]]