root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Fix broken links to XSD schemas in ref docs 

Closes gh-26129
This commit is contained in:
Sam Brannen 2020-11-23 14:49:43 +01:00
parent 7c47f554c0
commit 4ed645e710
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/docs/asciidoc/core/core-appendix.adoc
View File

@ -666,7 +666,8 @@ integrate such parsers into the Spring IoC container.
To facilitate authoring configuration files that use a schema-aware XML editor, To facilitate authoring configuration files that use a schema-aware XML editor,
Spring's extensible XML configuration mechanism is based on XML Schema. If you are not Spring's extensible XML configuration mechanism is based on XML Schema. If you are not
familiar with Spring's current XML configuration extensions that come with the standard familiar with Spring's current XML configuration extensions that come with the standard
Spring distribution, you should first read the appendix entitled <<appendix.adoc#xsd-configuration>>. Spring distribution, you should first read the previous section on <<xsd-schemas>>.
To create new XML configuration extensions: To create new XML configuration extensions:

6
src/docs/asciidoc/languages/dynamic-languages.adoc
View File

@ -92,7 +92,7 @@ container. Using the dynamic-language-backed beans with a plain `BeanFactory`
implementation is supported, but you have to manage the plumbing of the Spring internals implementation is supported, but you have to manage the plumbing of the Spring internals
to do so. to do so.
For more information on schema-based configuration, see <<appendix.adoc#xsd-configuration, For more information on schema-based configuration, see <<xsd-schemas-lang,
XML Schema-based Configuration>>. XML Schema-based Configuration>>.
==== ====
@ -176,7 +176,7 @@ of your dynamic language source files.
The final step in the list in the <<dynamic-language-beans-concepts, preceding section>> The final step in the list in the <<dynamic-language-beans-concepts, preceding section>>
involves defining dynamic-language-backed bean definitions, one for each bean that you involves defining dynamic-language-backed bean definitions, one for each bean that you
want to configure (this is no different from normal JavaBean configuration). However, want to configure (this is no different from normal JavaBean configuration). However,
instead of specifying the fully qualified classname of the class that is to be instead of specifying the fully qualified class name of the class that is to be
instantiated and configured by the container, you can use the `<lang:language/>` instantiated and configured by the container, you can use the `<lang:language/>`
element to define the dynamic language-backed bean. element to define the dynamic language-backed bean.
@ -848,7 +848,7 @@ The `lang` elements in Spring XML configuration deal with exposing objects that
written in a dynamic language (such as Groovy or BeanShell) as beans in the Spring container. written in a dynamic language (such as Groovy or BeanShell) as beans in the Spring container.
These elements (and the dynamic language support) are comprehensively covered in These elements (and the dynamic language support) are comprehensively covered in
<<integration.adoc#dynamic-language, Dynamic Language Support>>. See that chapter <<dynamic-language, Dynamic Language Support>>. See that section
for full details on this support and the `lang` elements. for full details on this support and the `lang` elements.
To use the elements in the `lang` schema, you need to have the following preamble at the To use the elements in the `lang` schema, you need to have the following preamble at the