[jboss-cvs] JBossAS SVN: r104281 - in projects/snowdrop/examples/trunk/sportsclub: sportsclub-invoicing-webmvc/src/main/webapp/WEB-INF and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Apr 27 16:05:25 EDT 2010
Author: marius.bogoevici
Date: 2010-04-27 16:05:24 -0400 (Tue, 27 Apr 2010)
New Revision: 104281
Modified:
projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Introduction.xml
projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Modules.xml
projects/snowdrop/examples/trunk/sportsclub/sportsclub-invoicing-webmvc/src/main/webapp/WEB-INF/spring-business-context.xml
Log:
some adjustments
Modified: projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Introduction.xml
===================================================================
--- projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Introduction.xml 2010-04-27 19:06:22 UTC (rev 104280)
+++ projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Introduction.xml 2010-04-27 20:05:24 UTC (rev 104281)
@@ -31,12 +31,6 @@
</section>
<section>
- <title>Taking a first glance at the sources</title>
-
- <para></para>
- </section>
-
- <section>
<title>How to run the examples</title>
<para>Running the application consists of the following
@@ -148,8 +142,10 @@
<simplesect>
<title>Deploying</title>
- <para>Deploying the application is as easy as copying one of the jars
- produced by the application</para>
+ <para>Deploying the application is as easy as copying one of the EARs
+ produced by the application into the $JBOSS_HOME/servers/default/deploy
+ folder. You can do that either before starting the application server,
+ or after it has started. Before you deploy the application</para>
</simplesect>
</section>
</chapter>
Modified: projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Modules.xml
===================================================================
--- projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Modules.xml 2010-04-27 19:06:22 UTC (rev 104280)
+++ projects/snowdrop/examples/trunk/sportsclub/docs/guide/en-US/Modules.xml 2010-04-27 20:05:24 UTC (rev 104281)
@@ -95,13 +95,13 @@
<entry>The application uses JBoss-deployed EJBs which are
injected with Spring beans acquired from an application context
bootstrapped by the Spring Deployer. Transactions are managed by
- EJBs. </entry>
+ EJBs.</entry>
</row>
<row>
<entry>User Interface</entry>
- <entry>JSF/Richfaces and Spring integration </entry>
+ <entry>JSF/Richfaces and Spring integration</entry>
<entry>The application uses the JBoss AS-provided JSF support,
and Richfaces components. The business services and UI-backing
@@ -787,7 +787,7 @@
</section>
<section>
- <title>An problem of reusing content</title>
+ <title>A problem of reusing content</title>
<para>Having three different web applications to be included in the same
package raises the problem of reusing some content. Surely, the images
@@ -811,8 +811,8 @@
building and deploying the application through the IDE, without
Maven. This does not affect the general functionality of the
application but may affect the look and feel in that particular
- situation. However, if the application is build using Maven this
- will not be a problem.</para>
+ situation. However, if the application is build using Maven,
+ this will not be a problem.</para>
</note></para>
</informalexample></para>
</section>
@@ -841,6 +841,39 @@
which in our case is a Spring bean. In order to take full advantage of
the managed environment provided by the application server, the Spring
bean will be invoked in a JCA context.</para>
+
+ <para>The component that processes JMS messages is a POJO:</para>
+
+ <para><informalexample>
+ <para><programlisting>@Component
+public class PaymentNotificationProcessor
+{
+
+ @Autowired
+ private PaymentProcessor paymentProcessor;
+
+ public void processPaymentNotification(PaymentNotification paymentNotification)
+ {
+ paymentProcessor.processPayment(paymentNotification.getAccountNumber(), paymentNotification.getAmount());
+ }
+
+}</programlisting></para>
+ </informalexample></para>
+
+ <para>It delegates the actual processing of a PaymentNotification to a
+ different component, the PaymentProcessor, which is injected in the
+ PaymentNotificationProcessor. This is done in order to maintain a degree
+ of separation between the way data may be represented when exchanged
+ over the messaging system (i.e. encapsulated in a PaymentNotification
+ object), and the contract of the internal component which actually does
+ the processing. The PaymentProcessor instance injected into the
+ PaymentNotificationProcessor is, in fact, reused by the
+ PaymentNotificationService web service implementation (whose contract
+ does not depend on the PaymentNotification entity). </para>
+
+ <para>Spring will instantiate a bean named
+ "paymentNotificationProcessor" which will be registered as a processor
+ for JMS message as follows:</para>
</section>
<section>
Modified: projects/snowdrop/examples/trunk/sportsclub/sportsclub-invoicing-webmvc/src/main/webapp/WEB-INF/spring-business-context.xml
===================================================================
--- projects/snowdrop/examples/trunk/sportsclub/sportsclub-invoicing-webmvc/src/main/webapp/WEB-INF/spring-business-context.xml 2010-04-27 19:06:22 UTC (rev 104280)
+++ projects/snowdrop/examples/trunk/sportsclub/sportsclub-invoicing-webmvc/src/main/webapp/WEB-INF/spring-business-context.xml 2010-04-27 20:05:24 UTC (rev 104281)
@@ -46,11 +46,6 @@
<bean id="mBeanServer" class="org.jboss.mx.util.MBeanServerLocator" factory-method="locateJBoss"/>
- <bean id="messageListener" class="org.springframework.jms.listener.adapter.MessageListenerAdapter">
- <property name="delegate" ref="paymentNotificationProcessor"/>
- <property name="defaultListenerMethod" value="processPaymentNotification"/>
- </bean>
-
<jee:jndi-lookup id="jcaConnectionFactory" jndi-name="java:/JmsXA"/>
<bean class="org.springframework.jms.core.JmsTemplate">
More information about the jboss-cvs-commits
mailing list