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