Update docs to use of @Bean inside a @Component

This commit is contained in:
Mark Pollack 2009-04-27 05:37:45 +00:00
parent cea8f7f69e
commit c2f4f97fa5
3 changed files with 420 additions and 379 deletions

File diff suppressed because it is too large Load Diff

View File

@ -1,7 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
<chapter id="new-in-3"> <chapter id="new-in-3">
<title>What's new in Spring 3.0?</title> <title>What's new in Spring 3.0?</title>
@ -178,8 +177,9 @@
</listitem> </listitem>
<listitem> <listitem>
<para>Object to XML mapping functionality (OXM) moved from Spring Web Services project</para> <para>Object to XML mapping functionality (OXM) moved from Spring Web
</listitem> Services project</para>
</listitem>
<listitem> <listitem>
<para>Comprehensive REST support</para> <para>Comprehensive REST support</para>
@ -348,32 +348,33 @@ public class AppConfig{
</section> </section>
<section> <section>
<title>Factory Bean definitions using annotations</title> <title>Defining bean metadata within components</title>
<para>FactoryBeans can be defined within a Spring component definition <para><literal>@Bean</literal> annotated methods are also supported
and registered using standard component-scanning techniques. See <link inside Spring components. They contribute a factory bean definition to
linkend="beans-factorybeans-annotations">Factory Bean Definitions the container. See <link
using annotations</link> for more information</para> linkend="beans-factorybeans-annotations">Defining bean metadata within
components</link> for more information</para>
</section> </section>
</section> </section>
<section id="new-feature-oxm"> <section id="new-feature-oxm">
<title>The Data Tier</title> <title>The Data Tier</title>
<para>Object to XML mapping functionality (OXM) from the Spring Web Services project have <para>Object to XML mapping functionality (OXM) from the Spring Web
been moved to the core Spring Framework now. The functionality is found in the Services project have been moved to the core Spring Framework now. The
<literal>org.springframework.oxm</literal> package. More information on functionality is found in the <literal>org.springframework.oxm</literal>
the use of the <literal>OXM</literal> can be found package. More information on the use of the <literal>OXM</literal> can
in the <link linkend="oxm">Marshalling XML using O/X Mappers</link> chapter.</para> be found in the <link linkend="oxm">Marshalling XML using O/X
Mappers</link> chapter.</para>
</section> </section>
<section id="new-feature-rest"> <section id="new-feature-rest">
<title>The Web Tier</title> <title>The Web Tier</title>
<para>The most exciting new feature for the Web Tier is the support for building <para>The most exciting new feature for the Web Tier is the support for
RESTful web services and web applications. There are also some new annotations that building RESTful web services and web applications. There are also some
can be used in any web application.</para> new annotations that can be used in any web application.</para>
<section> <section>
<title>Comprehensive REST support</title> <title>Comprehensive REST support</title>
@ -387,14 +388,14 @@ public class AppConfig{
functionality make use of functionality make use of
<interfacename>HttpConverter</interfacename>s to facilitate the <interfacename>HttpConverter</interfacename>s to facilitate the
conversion between objects and their representation in HTTP request conversion between objects and their representation in HTTP request
and replies. </para> and replies.</para>
<para>The <classname>MarhsallingHttpMessageConverter</classname> uses <para>The <classname>MarhsallingHttpMessageConverter</classname> uses
the <emphasis>Object to XML mapping</emphasis> functionality mentioned earlier.</para> the <emphasis>Object to XML mapping</emphasis> functionality mentioned
earlier.</para>
<para>Refer to the section on <link linkend="rest">REST support</link> <para>Refer to the section on <link linkend="rest">REST support</link>
for more information.</para> for more information.</para>
</section> </section>
<section> <section>
@ -407,7 +408,6 @@ public class AppConfig{
@CookieValue annotation</link> and <link @CookieValue annotation</link> and <link
linkend="mvc-ann-requestheader">Mapping request header attributes with linkend="mvc-ann-requestheader">Mapping request header attributes with
the @RequestHeader annotation</link> for more information.</para> the @RequestHeader annotation</link> for more information.</para>
</section> </section>
</section> </section>
@ -422,10 +422,11 @@ public class AppConfig{
<section id="new-feature-jee-6"> <section id="new-feature-jee-6">
<title>Early support for Java EE 6</title> <title>Early support for Java EE 6</title>
<para>We provide support for asynchronous method invocations through the use of <para>We provide support for asynchronous method invocations through the
the new @Async annotation (or EJB 3.1's @Asynchronous annotation).</para> use of the new @Async annotation (or EJB 3.1's @Asynchronous
annotation).</para>
<para>JSF 2.0, JPA 2.0, etc</para> <para>JSF 2.0, JPA 2.0, etc</para>
<para>Work in progress... not part of the Spring 3.0 M3 release.</para> <para>Work in progress... not part of the Spring 3.0 M3 release.</para>
</section> </section>

View File

@ -853,8 +853,10 @@ URI location = template.postForLocation(uri, booking, String.class, "1");
<section id="rest-message-conversion"> <section id="rest-message-conversion">
<title>HTTP Message Conversion</title> <title>HTTP Message Conversion</title>
<para>Objects passed to and returned from the methods getForObject(), <para>Objects passed to and returned from the methods
postForLocation(), and put() and are converted to HTTP requests and from <methodname>getForObject</methodname>,
<methodname>postForLocation</methodname>, and
<methodname>put</methodname> are converted to HTTP requests and from
HTTP responses by <interfacename>HttpMessageConverters</interfacename>. HTTP responses by <interfacename>HttpMessageConverters</interfacename>.
The <interfacename>HttpMessageConverter</interfacename> interface is The <interfacename>HttpMessageConverter</interfacename> interface is
show below to give you a better feel for its functionality</para> show below to give you a better feel for its functionality</para>