From 752bbbdd056459df039c0b29d4da5e1b44b3b5bc Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Mon, 29 Dec 2014 10:54:19 +0100 Subject: [PATCH] Fix scope inheritance documentation Issue: SPR-12570 --- src/asciidoc/index.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/asciidoc/index.adoc b/src/asciidoc/index.adoc index cfc6d91a09c..b2415a49eb2 100644 --- a/src/asciidoc/index.adoc +++ b/src/asciidoc/index.adoc @@ -4707,13 +4707,13 @@ A child bean definition uses the bean class from the parent definition if none i specified, but can also override it. In the latter case, the child bean class must be compatible with the parent, that is, it must accept the parent's property values. -A child bean definition inherits constructor argument values, property values, and -method overrides from the parent, with the option to add new values. Any initialization +A child bean definition inherits scope, constructor argument values, property values, and +method overrides from the parent, with the option to add new values. Any scope, initialization method, destroy method, and/or `static` factory method settings that you specify will override the corresponding parent settings. The remaining settings are __always__ taken from the child definition: __depends on__, -__autowire mode__, __dependency check__, __singleton__, __scope__, __lazy init__. +__autowire mode__, __dependency check__, __singleton__, __lazy init__. The preceding example explicitly marks the parent bean definition as abstract by using the `abstract` attribute. If the parent definition does not specify a class, explicitly