Fixed @Configurable documentation with respect to logging when the aspect hasn't been configured

Issue: SPR-10295
This commit is contained in:
Juergen Hoeller 2013-02-15 13:30:34 +01:00 committed by unknown
parent 81a929aed3
commit f0787bdb86
1 changed files with 2 additions and 2 deletions

View File

@ -2969,8 +2969,8 @@ public class AppConfig {
<para>Instances of <interfacename>@Configurable</interfacename> objects <para>Instances of <interfacename>@Configurable</interfacename> objects
created <emphasis>before</emphasis> the aspect has been configured will created <emphasis>before</emphasis> the aspect has been configured will
result in a warning being issued to the log and no configuration of the result in a message being issued to the debug log and no configuration
object taking place. An example might be a bean in the Spring of the object taking place. An example might be a bean in the Spring
configuration that creates domain objects when it is initialized by configuration that creates domain objects when it is initialized by
Spring. In this case you can use the "depends-on" bean attribute to Spring. In this case you can use the "depends-on" bean attribute to
manually specify that the bean depends on the configuration manually specify that the bean depends on the configuration