[jboss-cvs] JBossAS SVN: r111069 - projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Mar 30 08:23:43 EDT 2011
Author: rebecca_newton
Date: 2011-03-30 08:23:42 -0400 (Wed, 30 Mar 2011)
New Revision: 111069
Modified:
projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Getting_Started_Introductory_Example.xml
projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Migration_Guide.xml
projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Spring_On_JBoss_Best_Practices.xml
Log:
line edits
Modified: projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Getting_Started_Introductory_Example.xml
===================================================================
--- projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Getting_Started_Introductory_Example.xml 2011-03-30 09:49:21 UTC (rev 111068)
+++ projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Getting_Started_Introductory_Example.xml 2011-03-30 12:23:42 UTC (rev 111069)
@@ -37,7 +37,7 @@
</itemizedlist>
<section>
- <title>Assumptions and placeholder names</title>
+ <title>Assumptions and Placeholder Names</title>
<para>This tutorial assumes that the location of
JBoss Enterprise Application is $EAP_HOME, which represents the
@@ -482,7 +482,7 @@
controller bean automatically if it finds the class on the classpath.
The @Autowired annotation is similar to the previous example,
instructing Spring to inject a UserDao instance automatically. Specific
- to this class, however, are the MVC annotations: @RequestMapping,
+ to this class, however, are the MVC annotations; @RequestMapping,
@RequestParam and @ModelAttribute.</para>
<para>The @RequestMapping annotation is added at the class level to map
@@ -502,7 +502,7 @@
bind the 'username' value submitted by the form to the method
parameter.</para>
- <para>To finalize the code, a view that renders the form will be created.
+ <para>To finalize the code, a view that renders the form is created.
When the page is initially rendered, it will display the warning message
returned by getInitialMessage(). After each submission, the page will
display a welcome message with the full name of the user. So, create a
@@ -721,26 +721,42 @@
</beans></programlisting>
- <para>First, Spring was instructed to scan the package
- 'org.jboss.spring.getting.started.domain' for component beans, looking
+ <para>
+ The instructions given to Spring in the file are as follows:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>Spring was instructed to scan the package 'org.jboss.spring.getting.started.domain' for component beans, looking
for specific annotations such as @Service, and inject them automatically
- based on the @Autowired annotation. In this case, this will create the
- bean definition for UserDao. Then, beans are created for the data source
- and the entity manager, because a managed data source is being used, as well as a
- container-managed entity manager. The management strategy is set to JTA,
+ based on the @Autowired annotation. </para>
+ <para>
+ In this case, this will create the
+ bean definition for UserDao.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Beans are created for the data source and the entity manager. This is because a managed data source is being used, as well as a container-managed entity manager.</para>
+ <para>
+ The management strategy is set to JTA,
and Spring is instructed to apply transactions declaratively, based on the
- @Transactional annotations found on bean classes. Since this is a demo
- example, we need to initialize the database and we instruct Spring to
- run the init-db.sql script at startup.</para>
+ @Transactional annotations found on bean classes.
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ Since this is an example, the database needs to be initialized and Spring instructed to
+ run the init-db.sql script at startup.
+ </para>
- <para>The front-end component that are used to configure the dispatcher
- servlet are defined in a file named 'spring-mvc-context.xml'. Follow the
- same steps as with the business context and select the namespace bean,
+ <para>The front-end components that are used to configure the dispatcher
+ servlet are defined in a file named <filename>spring-mvc-context.xml</filename>.
+ Follow the same steps as with the business context and select the namespace bean,
context and mvc in the dialog. The configuration file is structured as
follows:</para>
<example>
- <title>Dispatcher servlet configuration file</title>
+ <title>Dispatcher Servlet Configuration File</title>
<para><programlisting language="XML"><beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:context="http://www.springframework.org/schema/context"
@@ -763,7 +779,7 @@
</example>
<para>Using this context definition, Spring will scan for component
- beans (such as the UserController), and will use the mappings defined by
+ beans (such as the UserController), and use the mappings defined by
the annotations found on controller beans. Finally, after a controller
is executed, the InternalResourceViewResolver will determine a jsp page
that DispatcherServlet will forward the request for rendering the
@@ -773,40 +789,62 @@
<section>
<title>Running the example</title>
- <para>Finally, you need to run the example. You can do this either from
- the command line or from JBDS. Here is what you need to do in each
+ <para>Finally, you need to run the example. This can be done either from
+ the command line or from JBoss Developer Studio. Here is what you need to do in each
case.</para>
<simplesect>
- <title>Running the example from command line</title>
+ <title>Running the Example from Command Line</title>
- <para>You need to build the example with Maven. Afterwards you can
+ <para>Build the example with Maven. Afterwards you can
deploy it by copying it into
- $EAP_HOME/jboss-as/server/<profile>/deploy.</para>
+ <filename>$EAP_HOME/jboss-as/server/<profile>/deploy</filename>.</para>
<example>
- <title>Building and deploying example from the command line</title>
+ <title>Building and Deploying Example From the Command Line</title>
- <programlisting>cd $EXAMPLE_HOME;
+ <programlisting>
+cd $EXAMPLE_HOME;
mvn clean package
cp target/getting-started.war $EAP_HOME/jboss-as/server/<profile>/deploy
</programlisting>
</example>
+ <para>After deploying the example and starting JBoss EAP, the example
+ can be accessed at
+ <uri>http://localhost:8080/getting-started</uri>.</para>
</simplesect>
<simplesect>
- <title>Running the example from JBDS</title>
+ <title>Running the Example from JBoss Developer Studio</title>
- <para>You can also run the example from JBDS directly. In order to do
- so open the contextual menu for the project (i.e. click right on the
- project in the projects list), then 'Run As'->'Run on Server',
- choose a JBoss EAP 5.1 instance and click Finish. If you don't find a
- JBoss EAP instance, please refer to Appendix B for details.</para>
- </simplesect>
-
- <simplesect>
- <title>Accessing the running example</title>
-
+ <para>The example can also be run from JBoss Developer Studio directly.
+ To do so, follow these steps.
+ </para>
+ <procedure>
+ <step>
+ <para>
+ Right click on the project in the projects list to bring up the contextual menu for the project.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click <guibutton>Run As</guibutton>, then <guibutton>Run on Server</guibutton>
+ </para>
+ </step>
+ <step>
+ <para>
+ Choose the JBoss Enterprise Application Platform 5.1 instance.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click <guibutton>Finish</guibutton>
+ </para>
+ <para>
+ If you don't find a JBoss Enterprise Application Platform instance, refer to Appendix B.
+ </para>
+ </step>
+ </procedure>
<para>After deploying the example and starting JBoss EAP, the example
can be accessed at
<uri>http://localhost:8080/getting-started</uri>.</para>
@@ -815,12 +853,12 @@
</section>
<section>
- <title>Creating a simple Eclipse project</title>
+ <title>Creating a Simple Eclipse Project</title>
<para>A simple (non-Maven based) Eclipse project will be similar to the
Maven-based one. The content of the component classes and bean definitions
is identical, the main difference being the location of source folders and
the need to manually add the dependencies to the project and selecting the
- ones that need to be exported (i.e. included in the deployed WAR.</para>
+ ones that need to be exported (that is, included in the deployed WAR).</para>
</section>
</chapter>
Modified: projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Migration_Guide.xml
===================================================================
--- projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Migration_Guide.xml 2011-03-30 09:49:21 UTC (rev 111068)
+++ projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Migration_Guide.xml 2011-03-30 12:23:42 UTC (rev 111069)
@@ -335,11 +335,11 @@
details about using the LocalContainerEntityManagerFactoryBean in JBoss and
its implications, please refer to the previous chapter.</para>
- <example>
+ <example id="jpa-pu-with-alternate-pxml">
<title>LocalContainerEntityManagerFactoryBean with alternate
persistence.xml location</title>
- <programlisting id="jpa-pu-with-alternate-pxml" language="XML"><bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
+ <programlisting language="XML"><bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="persistenceXmlLocation" value="classpath*:META-INF/jpa-persistence.xml"/>
<!-- other properties (ommitted) -->
</bean></programlisting>
Modified: projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Spring_On_JBoss_Best_Practices.xml
===================================================================
--- projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Spring_On_JBoss_Best_Practices.xml 2011-03-30 09:49:21 UTC (rev 111068)
+++ projects/docs/enterprise/WFK/Spring_Developer_Guide/en-US/Spring_On_JBoss_Best_Practices.xml 2011-03-30 12:23:42 UTC (rev 111069)
@@ -9,7 +9,7 @@
<para>The Spring Framework is a flexible environment for developing
enterprise applications. This means that the developer can choose
- between a number of alternatives when it comes to accessing middleware
+ between a number of alternatives for accessing middleware
services.</para>
<para>JBoss is a feature-rich application server, which provides a complex
@@ -55,8 +55,9 @@
file.</para>
<para>The definition for such a datasource is included in a file
- that ends in -ds.xml (for example, <filename>sportsclub-ds.xml</filename>) and can either
- be copied in the deploy directory of the target JBoss AS configuration for
+ that ends in -ds.xml (for example, <filename>sportsclub-ds.xml</filename>). It can either
+ be copied into the deploy directory of the target JBoss application
+ server configuration for
deployment at startup, or be included in the META-INF directory
of the application for being deployed together with the
application.</para>
@@ -94,7 +95,7 @@
<para>Applications that use Hibernate directly (as opposed to JPA)
should take advantage of the fact that Hibernate is already included in
- the application server. Therefore, applications do not need to include a
+ the application server. This means that applications do not need to include a
Hibernate distribution.</para>
<para>Spring applications can use one of Spring's
@@ -102,15 +103,17 @@
previous section for details).</para>
<example>
- <title>SessionFactory bean definition</title>
- <programlisting language="XML"><bean id="sessionFactory" class="org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBean">
+ <title>SessionFactory Bean Definition</title>
+ <programlisting language="XML">
+<bean id="sessionFactory" class="org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBean">
<property name="dataSource" ref="dataSource"/>
...
</bean></programlisting>
</example>
<para>JTA transaction management and Hibernate-JTA session
- management integration is recommended by setting up the following properties:</para>
+ management integration is recommended. You can use these by
+ setting up the following properties:</para>
<example>
<title>JTA session management setup properties</title>
@@ -124,9 +127,9 @@
component classes such as DAOs and used directly as in the following
example:</para>
-<!-- <example>
- <title>Hibernate-based DAO: a SessionFactory is injected directly in
- the bean</title> -->
+ <example>
+ <title>Hibernate-based DAO: a SessionFactory is Injected Directly in
+ the Bean</title>
<programlisting language="Java">public class HibernateAccountDao {
@Autowired SessionFactory sessionFactory;
@@ -136,27 +139,28 @@
}
...
}</programlisting>
- <!-- </example> -->
+ </example>
+
<para>A comprehensive example of using Hibernate-driven data access in
- Spring-based applications can be found in the Sportsclub demo
- application, included in the Web Framework Kit distribution.</para>
+ Spring-based applications can be found in the Sportsclub example
+ application. It can be found in your distribution of JBoss Web Framework Kit.</para>
</section>
-
- <section>
+ </section>
+ <section>
<title>Using JPA</title>
<section>
<title>PersistenceUnit Deployed by the Container</title>
<para>Spring applications can retrieve the persistence units deployed
- by the container by looking them up in JNDI. In order to be able to
+ by the container by looking them up in JNDI. In order to
bind the entity manager or entity manager factory under a
well-established name and subsequently look them up, applications can
use special Hibernate configuration properties.</para>
<example>
- <title>Persistence unit definition</title>
+ <title>Persistence Unit Definition</title>
<programlisting language="XML"><persistence xmlns="http://java.sun.com/xml/ns/persistence" version="1.0">
<persistence-unit name="sportsclubPU">
@@ -177,7 +181,7 @@
Spring Bean as follows:</para>
<example>
- <title>Spring bean representing a container-managed entity
+ <title>Spring Bean Representing a Container-managed Entity
manager</title>
<programlisting language="XML"><jee:jndi-lookup id="entityManager" jndi-name="java:/example/em"/></programlisting>
@@ -187,8 +191,8 @@
component classes such as DAOs. <!-- When doing so, the COMMENTED OUT UNTIL THE SENTENCE IS COMPLETE--></para>
<example>
- <title>Hibernate-based DAO: a SessionFactory is injected directly in
- the bean</title>
+ <title>Hibernate-based DAO: a SessionFactory is Injected Directly in
+ the Bean</title>
<programlisting language="Java">public class HibernateAccountDao {
@Autowired EntityManager entityManager;
@@ -211,7 +215,9 @@
<programlisting language="XML"><jee:jndi-lookup id="entityManagerFactory" jndi-name="java:/example/emf"/></programlisting>
</example>
- <para>In general, for implementing transaction-aware components, it is not typical to access EntityManagerFactories directly (for example a service that delegates to multiple DAOs which have to be
+ <para>In general, for implementing transaction-aware components,
+ it is not typical to access EntityManagerFactories directly
+ (for example a service that delegates to multiple DAOs which have to be
enrolled in the same transaction). This is true even if Spring supports injection
into fields annotated with @PersistenceContext when an
EntityManagerFactory is provided. Rather, components should access the
@@ -219,18 +225,19 @@
with non-Spring components that use JPA as well (for example EJBs).</para>
<para>A comprehensive example of using JPA-driven data access in
- Spring-based applications can be found in the Sportsclub demo
+ Spring-based applications can be found in the Sportsclub example
application, included in the Web Framework Kit distribution.</para>
</section>
<section>
- <title>PersistenceUnit created by Spring</title>
+ <title>PersistenceUnit Created by Spring</title>
- <para>One important limitation of working with JNDI-bound
+ <para><!--One important limitation of working with JNDI-bound
EntityManagers and EntityManagerFactories is the lack of support for
- read-only transactions in Spring. When declaring transactions, Spring
- applications may specify that the transaction is intended to be
- read-only as in example</para>
+ read-only transactions in Spring. --> When declaring transactions, Spring
+ applications may specify that a transaction is intended to be
+ read-only as in example <xref linkend="transactional-method-read-only"/>.
+ </para>
<example id="transactional-method-read-only">
<title>A Spring Method Declaring a Read-Only Transaction</title>
@@ -250,7 +257,7 @@
using Hibernate as a persistence provider, underlying SessionFactory)
from being automatically flushed upon commit. The expected benefit of
this operation mode is a performance increase, as the persistence
- context will be simply discarded when the transaction ends. It should
+ context will be discarded when the transaction ends. It should
be noted that support for this mode is not obligatory in Spring, and
applications are not expected to rely on this behaviour at all time.
<!-- (cf. Spring reference documentation for details).--></para>
@@ -265,7 +272,7 @@
example of a bean definition for JBoss is provided here:</para>
<example>
- <title>A Spring-defined JTA-based entity manager factory</title>
+ <title>A Spring-defined JTA-based Entity Manager Factory</title>
<programlisting language="XML"><bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="jpaVendorAdapter">
@@ -290,7 +297,7 @@
</example>
<example id="alt-location">
- <title>Using an alternative location for persistence.xml</title>
+ <title>Using an Alternative Location for Persistence.xml</title>
<programlisting language="XML"><bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="persistenceXmlLocation" value="classpath*:META-INF/persistence-booking.xml"/>
<!-- other properties (ommitted) -->
@@ -328,8 +335,8 @@
the following example:</para>
<example>
- <title>Example of a PersistenceUnitPostProcessor implementation that
- adds all classes annotated with @Entity</title>
+ <title>Example of a PersistenceUnitPostProcessor Implementation That
+ Adds all Classes Annotated with @Entity</title>
<programlisting language="Java">package org.springframework.webflow.samples.booking;
@@ -378,8 +385,8 @@
LocalContainerEntityManagerFactoryBean as follows:
</para>
<example>
- <title>Adding the PersistenceUnitPostProcessor to the context
- definition</title>
+ <title>Adding the PersistenceUnitPostProcessor to the Context
+ Definition</title>
<programlisting language="XML"><bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<!-- other properties -->
<property name="persistenceUnitPostProcessors">
@@ -423,11 +430,11 @@
this can be set up through the metadata-complete attribute
(applications that use the Servlet 2.4 standard do not exhibit this
problem at all, since annotation-based injection is not supported by
- the container) .</para>
+ the container).</para>
<example>
- <title>The metadata-complete flag can be used to disable class
- scanning by JBoss</title>
+ <title>The Metadata-complete Flag Can Be Used to Disable Class
+ Scanning by JBoss</title>
<programlisting language="XML"><web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -452,16 +459,15 @@
</example>
<example>
- <title>Using a SharedEntityManager bean to create an injectable
- transaction-aware EntityManager</title>
+ <title>Using a SharedEntityManager Bean to Create an Injectable
+ Transaction-aware EntityManager</title>
<programlisting language="XML"><bean id="entityManagerWrapper" class="org.springframework.orm.jpa.support.SharedEntityManagerBean">
<property name="entityManagerFactory" ref="entityManagerFactory"/>
</bean></programlisting>
</example>
</section>
- </section>
- </section>
+
<section id="messaging_integration">
<title>Messaging (JMS) Integration</title>
@@ -502,15 +508,15 @@
</example>
<para>Spring provides two dfferent types of MessageListenerContainers;
- 'native' JMS, and JCA-based. Using the JCA MessageListenerContainer
- on JBoss Enterprise Application Platform, due to better integration with the
- application server for message delivery and session,
- connection, and message consumer management. In order to minimize the
+ 'native' JMS, and JCA-based. The Enterprise Application Platform uses
+ the JCA MessageListenerContainer due to better integration with the
+ application server for server message and delivery session, connection,
+ and message consumer management. In order to minimize the
amount of proprietary code, Snowdrop's namespace support for
JMS/JCA integration can be used <!--(see Snowdrop documentation for details) -->.</para>
<example>
- <title>Using the JCA message listener containers and namespace support
+ <title>Using the JCA Message Listener Containers and Namespace Support
in JBoss</title>
<programlisting language="XML"> <jms:jca-listener-container resource-adapter="resourceAdapter" acknowledge="auto"
activation-spec-factory="activationSpecFactory">
@@ -544,7 +550,7 @@
or via XML. An example using annotations can be found in <xref
linkend="transactional-method-read-only" /> and more extensively in the
Sportsclub example application. It is
- important to note that the model is the same regardless whether the
+ important to note that the model is the same regardless of whether the
transactions being used are local transactions or JTA transactions.
Spring will wrap components in a transactional proxy which will delegate
to a transaction manager; which is declared separately as a Spring bean.
@@ -559,7 +565,7 @@
transaction manager definition.</para>
<example>
- <title>JTA transaction manager definition in Spring</title>
+ <title>JTA Transaction Manager Definition in Spring</title>
<programlisting language="XML"><tx:jta-transaction-manager id="transactionManager"/></programlisting>
</example>
@@ -598,8 +604,8 @@
<title>EJB Integration</title>
<para>Although there is overlap between EJB and Spring,
- mixing the two component models together is a frequently encountered
- scenario. It consists of having components of one type delegating
+ mixing the two component models together is common. It consists of
+ having components of one type delegating
functionality to components of the other type. The best practice is to
provide the delegate components via injection, which can happen in any
direction (Spring to EJB and EJB to Spring).</para>
@@ -607,7 +613,8 @@
<section>
<title>Injecting Spring Beans Into EJBs</title>
- <para>For JBoss Enterprise Application Platform 5 there are two major options of injecting Spring
+ <para>For JBoss Enterprise Application Platform 5 there are two
+ major options of injecting Spring
beans into EJBs:</para>
<itemizedlist>
@@ -628,8 +635,8 @@
annotation.</para>
<example>
- <title>Injecting a Spring Bean into EJBs using Spring's native
- support</title>
+ <title>Injecting a Spring Bean into EJBs Using Spring's Native
+ Support</title>
<programlisting language="Java">@Stateless
@Interceptors(SpringBeanAutowiringInterceptor.class)
@@ -652,8 +659,8 @@
file.</para>
<example id="singletonBFL">
- <title>Simple beanRefContext.xml file used by a
- ContextSingletonBeanFactoryLocator and the corresponding
+ <title>Simple beanRefContext.xml File Used by a
+ ContextSingletonBeanFactoryLocator and the Corresponding
simpleContext.xml</title>
<programlisting language="XML"><beans>
@@ -666,9 +673,9 @@
<bean id="springBean" class="example.SpringBean"/>
</beans></programlisting>
- <para>For more details, including how to customize the behaviour of
+ <!-- <para>For more details, including how to customize the behaviour of
SpringBeanAutowiringInterceptor, please consult the Spring Framework
- reference documentation.</para>
+ reference documentation.</para> -->
</example>
</simplesect>
@@ -680,7 +687,7 @@
overview on how to inject Spring beans into EJBs using Snowdrop
support. For more details and a more elaborate example, please consult
the <citetitle>Snowdrop User Guide</citetitle> and the
- <citetitle>portsclub Example</citetitle>.</para>
+ <citetitle>Sportsclub Example</citetitle>.</para>
<para>Snowdrop supports the bootstrapping of Spring application
contexts through its JBoss-specific Spring deployer. This
@@ -692,7 +699,7 @@
from within the context definition.</para>
<example id="spring-deployer-xml">
- <title>Spring beans configuration file (example-spring.xml)</title>
+ <title>Spring Beans Configuration File (example-spring.xml)</title>
<programlisting language="XML"><beans>
<description>BeanFactory=(MyApp)</description>
@@ -710,7 +717,7 @@
annotation.</para>
<example>
- <title>Injecting a Spring bean into an EJB using Snowdrop</title>
+ <title>Injecting a Spring Bean into an EJB Using Snowdrop</title>
<programlisting language="Java">@Stateless
@Interceptors(SpringLifecycleInterceptor.class)
@@ -726,10 +733,10 @@
</section>
<section>
- <title>Accessing EJBs from Spring beans</title>
+ <title>Accessing EJBs from Spring Beans</title>
<para>Injecting stateless EJBs in Spring components is also possible.
- There are two possible ways:</para>
+ There are two ways this can be done:</para>
<itemizedlist>
<listitem>
@@ -746,7 +753,7 @@
in example <xref linkend="ejb-reference" /></para>
<example id="ejb-reference">
- <title>Defining an EJB reference as a Spring bean</title>
+ <title>Defining an EJB Reference as a Spring Bean</title>
<programlisting language="XML"><beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -766,7 +773,7 @@
</example>
<example>
- <title>Injecting an EJB reference defined as a Spring bean</title>
+ <title>Injecting an EJB Reference Defined as a Spring Bean</title>
<programlisting language="Java">public class ConsumerBean {
@@ -779,7 +786,7 @@
</example>
<example>
- <title>Injecting an EJB using annotations</title>
+ <title>Injecting an EJB Using Annotations</title>
<programlisting language="Java">public class ConsumerBean {
@@ -795,4 +802,5 @@
</example>
</section>
</section>
+ </section>
</chapter>
More information about the jboss-cvs-commits
mailing list