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

SPR-6257: Resolved in beans.xml

This commit is contained in:
David Syer 2009-10-27 11:56:06 +00:00
parent d0893c425e
commit 46818b038a
1 changed files with 46 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -3965,7 +3965,6 @@ org.springframework.scripting.groovy.GroovyMessenger@272961</programlisting>
<programlisting language="xml">&lt;bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"&gt; <programlisting language="xml">&lt;bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"&gt;
&lt;property name="locations" value="classpath:com/foo/jdbc.properties"/&gt; &lt;property name="locations" value="classpath:com/foo/jdbc.properties"/&gt;
&lt;/property&gt;
&lt;/bean&gt; &lt;/bean&gt;
&lt;bean id="dataSource" destroy-method="close" &lt;bean id="dataSource" destroy-method="close"
@ -4217,9 +4216,9 @@ dataSource.url=jdbc:mysql:mydb</programlisting>
url="http://static.springframework.org/spring/docs/3.0.x/javadoc-api/org/springframework/beans/factory/annotation/RequiredAnnotationBeanPostProcessor.html"><classname>RequiredAnnotationBeanPostProcessor</classname></ulink>.)</para> url="http://static.springframework.org/spring/docs/3.0.x/javadoc-api/org/springframework/beans/factory/annotation/RequiredAnnotationBeanPostProcessor.html"><classname>RequiredAnnotationBeanPostProcessor</classname></ulink>.)</para>
<note> <note>
<para><literal>&lt;context:annotation-config/&gt;</literal> <para><literal>&lt;context:annotation-config/&gt;</literal> only looks
only looks for annotations on beans in the same application context in for annotations on beans in the same application context in which it is
which it is defined. This means that, if you put defined. This means that, if you put
<literal>&lt;context:annotation-config/&gt;</literal> in a <literal>&lt;context:annotation-config/&gt;</literal> in a
<interfacename>WebApplicationContext</interfacename> for a <interfacename>WebApplicationContext</interfacename> for a
<classname>DispatcherServlet</classname>, it only checks for <classname>DispatcherServlet</classname>, it only checks for
@ -4270,9 +4269,10 @@ dataSource.url=jdbc:mysql:mydb</programlisting>
<interfacename>@Autowired</interfacename> in the examples below. <interfacename>@Autowired</interfacename> in the examples below.
<interfacename>@Inject</interfacename> does not have a required <interfacename>@Inject</interfacename> does not have a required
property unlike Spring's <interfacename>@Autowire</interfacename> property unlike Spring's <interfacename>@Autowire</interfacename>
annotation which has a <literal>required</literal> property to indicate if the value being annotation which has a <literal>required</literal> property to
injected is optional. This behavior is enabled automatically if you indicate if the value being injected is optional. This behavior is
have the JSR 330 JAR on the classpath.</para> enabled automatically if you have the JSR 330 JAR on the
classpath.</para>
</note> </note>
<programlisting language="java">public class SimpleMovieLister { <programlisting language="java">public class SimpleMovieLister {
@ -4443,11 +4443,11 @@ dataSource.url=jdbc:mysql:mydb</programlisting>
simplest case, this can be a plain descriptive value:</para> simplest case, this can be a plain descriptive value:</para>
<note> <note>
<para>JSR 330's <interfacename>@Qualifier</interfacename> <para>JSR 330's <interfacename>@Qualifier</interfacename> annotation
annotation can only be applied as a meta-annotation unlike Spring's can only be applied as a meta-annotation unlike Spring's @Qualifier
@Qualifier which takes a string property to discriminate among which takes a string property to discriminate among multiple injection
multiple injection candidates and can be placed on annotations as well candidates and can be placed on annotations as well as types, fields,
as types, fields, methods, constructors, and parameters.</para> methods, constructors, and parameters.</para>
</note> </note>
<programlisting language="java">public class MovieRecommender { <programlisting language="java">public class MovieRecommender {
@ -4968,9 +4968,10 @@ public @interface MovieQualifier {
project</ulink> are part of the core Spring Framework. This allows you project</ulink> are part of the core Spring Framework. This allows you
to define beans using Java rather than using the traditional XML files. to define beans using Java rather than using the traditional XML files.
Take a look at the <interfacename>@Configuration</interfacename>, Take a look at the <interfacename>@Configuration</interfacename>,
<interfacename>@Bean</interfacename>, <interfacename>@Import</interfacename>, and <interfacename>@Bean</interfacename>,
<interfacename>@DependsOn</interfacename> annotations for examples of how to use <interfacename>@Import</interfacename>, and
these new features.</para> <interfacename>@DependsOn</interfacename> annotations for examples of
how to use these new features.</para>
</note> </note>
<section id="beans-stereotype-annotations"> <section id="beans-stereotype-annotations">
@ -5089,9 +5090,9 @@ public class JpaMovieFinder implements MovieFinder {
component-scanning. The value of the component-scanning. The value of the
<interfacename>@Named</interfacename> property will be used as the <interfacename>@Named</interfacename> property will be used as the
Bean Name. At this time Spring defaults for bean scope will be applied Bean Name. At this time Spring defaults for bean scope will be applied
when using @Named. This behavior as well as mapping of JSR 330 and when using @Named. This behavior as well as mapping of JSR 330 and JSR
JSR 299 scopes is planned for Spring 3.0 GA assuming the JSRs are 299 scopes is planned for Spring 3.0 GA assuming the JSRs are stable
stable at that time.</para> at that time.</para>
</note> </note>
</section> </section>
@ -5315,9 +5316,10 @@ public class FactoryMethodComponent {
corresponding bean definition.</para> corresponding bean definition.</para>
<note> <note>
<para>JSR 330's @Named annotation can be used as a means to both detect <para>JSR 330's @Named annotation can be used as a means to both
components and to provide them with a name. This behavior is enabled detect components and to provide them with a name. This behavior is
automatically if you have the JSR 330 JAR on the classpath.</para> enabled automatically if you have the JSR 330 JAR on the
classpath.</para>
</note> </note>
<para>If such an annotation contains no <literal>name</literal> value or <para>If such an annotation contains no <literal>name</literal> value or
@ -6046,19 +6048,20 @@ argument.required=Ebagum lad, the '{0}' argument is required, I say, required.</
injected with the application context's injected with the application context's
<classname>MessageSource</classname> when the bean is created and <classname>MessageSource</classname> when the bean is created and
configured.</para> configured.</para>
<note> <note>
<para><emphasis>As an alternative to <para><emphasis>As an alternative to
<classname>ResourceBundleMessageSource</classname>, Spring provides <classname>ResourceBundleMessageSource</classname>, Spring provides a
a <classname>ReloadableResourceBundleMessageSource</classname> <classname>ReloadableResourceBundleMessageSource</classname> class.
class. This variant supports the same bundle file format but is more This variant supports the same bundle file format but is more flexible
flexible than the standard JDK based than the standard JDK based
<classname>ResourceBundleMessageSource</classname> <classname>ResourceBundleMessageSource</classname>
implementation.</emphasis> In particular, it allows for reading implementation.</emphasis> In particular, it allows for reading files
files from any Spring resource location (not just from the from any Spring resource location (not just from the classpath) and
classpath) and supports hot reloading of bundle property files supports hot reloading of bundle property files (while efficiently
(while efficiently caching them in between). Check out the caching them in between). Check out the
<classname>ReloadableResourceBundleMessageSource</classname> javadoc <classname>ReloadableResourceBundleMessageSource</classname> javadoc
for details.</para> for details.</para>
</note> </note>
</section> </section>
@ -6405,17 +6408,16 @@ argument.required=Ebagum lad, the '{0}' argument is required, I say, required.</
your application server's deployment directory.</para> your application server's deployment directory.</para>
<note> <note>
<para>Such RAR deployment units are usually self-contained; they do <para>Such RAR deployment units are usually self-contained; they do
not expose components to the outside world, not even to other not expose components to the outside world, not even to other modules
modules of the same application. Interaction with a RAR-based of the same application. Interaction with a RAR-based
ApplicationContext usually occurs through JMS destinations that it ApplicationContext usually occurs through JMS destinations that it
shares with other modules. A RAR-based ApplicationContext may also, shares with other modules. A RAR-based ApplicationContext may also,
for example, schedule some jobs, reacting to new files in the file for example, schedule some jobs, reacting to new files in the file
system (or the like). If it needs to allow synchronous access from system (or the like). If it needs to allow synchronous access from the
the outside, it could for example export RMI endpoints, which of outside, it could for example export RMI endpoints, which of course
course may be used by other application modules on the same may be used by other application modules on the same machine.</para>
machine.</para> </note>
</note>
</section> </section>
</section> </section>