From 4c08b3f5af7045bd8e3858a52813d6d8286c5313 Mon Sep 17 00:00:00 2001 From: canattofilipe Date: Mon, 10 Feb 2025 18:24:19 -0300 Subject: [PATCH] Fix: Adjust Bean Overview Doc to Start using getAutowireCapableBeanFactory Instead of getBeanFactory Signed-off-by: canattofilipe --- framework-docs/modules/ROOT/pages/core/beans/definition.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/framework-docs/modules/ROOT/pages/core/beans/definition.adoc b/framework-docs/modules/ROOT/pages/core/beans/definition.adoc index 766db398a19e..3a73b4087861 100644 --- a/framework-docs/modules/ROOT/pages/core/beans/definition.adoc +++ b/framework-docs/modules/ROOT/pages/core/beans/definition.adoc @@ -57,7 +57,7 @@ The following table describes these properties: In addition to bean definitions that contain information on how to create a specific bean, the `ApplicationContext` implementations also permit the registration of existing objects that are created outside the container (by users). This is done by accessing the -ApplicationContext's `BeanFactory` through the `getBeanFactory()` method, which returns +ApplicationContext's `BeanFactory` through the `getAutowireCapableBeanFactory()` method, which returns the `DefaultListableBeanFactory` implementation. `DefaultListableBeanFactory` supports this registration through the `registerSingleton(..)` and `registerBeanDefinition(..)` methods. However, typical applications work solely with beans defined through regular