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

fixed typos (SPR-7221)

This commit is contained in:
Juergen Hoeller 2010-05-20 08:16:49 +00:00
parent 469e30b507
commit ecf2d8c5de
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
spring-framework-reference/src/beans.xml
View File

@ -3667,7 +3667,7 @@ public final class Boot {
<para>When an <interfacename>ApplicationContext</interfacename> creates <para>When an <interfacename>ApplicationContext</interfacename> creates
a class that implements the a class that implements the
<interfacename>org.springframework.contxt.ApplicationContextAware</interfacename> <interfacename>org.springframework.context.ApplicationContextAware</interfacename>
interface, the class is provided with a reference to that interface, the class is provided with a reference to that
<interfacename>ApplicationContext</interfacename>.</para> <interfacename>ApplicationContext</interfacename>.</para>
@ -4532,7 +4532,7 @@ dataSource.url=jdbc:mysql:mydb</programlisting>
annotated classes are no longer POJOs and further more that the annotated classes are no longer POJOs and further more that the
configuration becomes decentralized and harder to control.</para> configuration becomes decentralized and harder to control.</para>
<para>No matter the choice, Spring can accomodate both styles and even <para>No matter the choice, Spring can accommodate both styles and even
mix them together. It's worth pointing out that through its <link mix them together. It's worth pointing out that through its <link
linkend="beans-java">JavaConfig</link> option, Spring allows annotations linkend="beans-java">JavaConfig</link> option, Spring allows annotations
to be used in a non-invasive way, without touching the target components to be used in a non-invasive way, without touching the target components
@ -6715,8 +6715,8 @@ public class AppConfig {
</para> </para>
<note> <note>
<para> <para>
Behaviour could be different according to the scope The behavior could be different according to the scope
of your bean. We are talking here about Singletons. of your bean. We are talking about singletons here.
</para> </para>
</note> </note>
<note> <note>