geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r917744 [19/31] - in /websites/production/geronimo/content: GMOxDOC20/ GMOxDOC20/geronimo-eclipse-plugin-installation-instructions.data/ cache/
Date Tue, 29 Jul 2014 00:52:21 GMT
Modified: websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-servlets-and-jsps-migration.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-servlets-and-jsps-migration.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-servlets-and-jsps-migration.html Tue Jul 29 00:52:18 2014
@@ -95,10 +95,10 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><p><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-top"></a><br clear="none">
+          <div class="wiki-content maincontent"><p><span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-top"></span><br clear="none">
 This article will help you migrate servlets and JSPs deployed JBoss v4 to Apache Geronimo. This article is part of a series of migration articles covering different types of applications migration.</p>
 
-<p>This article covers the migration one of the most fundamental aspects of J2EE; servlets and JSPs. The sample application used for this migration exercise is <a shape="rect" href="jboss-to-geronimo-servlets-and-jsps-migration.data/college_fest.zip?version=3&amp;modificationDate=1188483435000">College Fest</a> which just contains servlets and JSPs for handling the flow of control. The College Fest sample application does not use any database, for details on migrating JDBC applications refer to the <a shape="rect" href="jboss-to-geronimo-jdbc-migration.html" title="JBoss to Geronimo - JDBC Migration">JBoss to Geronimo - JDBC Migration</a> article.</p>
+<p>This article covers the migration one of the most fundamental aspects of J2EE; servlets and JSPs. The sample application used for this migration exercise is <a shape="rect" href="jboss-to-geronimo-servlets-and-jsps-migration.data/college_fest.zip?version=3&amp;modificationDate=1188483435000&amp;api=v2">College Fest</a> which just contains servlets and JSPs for handling the flow of control. The College Fest sample application does not use any database, for details on migrating JDBC applications refer to the <a shape="rect" href="jboss-to-geronimo-jdbc-migration.html">JBoss to Geronimo - JDBC Migration</a> article.</p>
 
 <p>After reading this article you should be able to reconfigure the JBoss build files and the deployment descriptors to set up the Apache Geronimo destination environment and then deploying simple Web applications.</p>
 
@@ -107,14 +107,14 @@ This article will help you migrate servl
 <ul><li><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-implementation">Servlets and JSPs implementation analysis</a></li><li><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-sampleApp">Sample application</a></li><li><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-JBoss">The JBoss environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-Geronimo">The Geronimo environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-migration">Step-by-step migration</a></li><li><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-summary">Summary</a></li></ul>
 
 
-<h1><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-ServletsandJSPsimplementationanalysis"></a>Servlets and JSPs implementation analysis <a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-implementation"></a></h1>
+<h1 id="JBosstoGeronimo-ServletsandJSPsMigration-ServletsandJSPsimplementationanalysisimplementation">Servlets and JSPs implementation analysis <span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-implementation"></span></h1>
 <p>Servlets and JSPs implementations may vary from one application server to another. The purpose of this section is to provide servlets and JSPs specific feature-to-feature comparison between JBoss and Apache Geronimo so you can clearly identify the differences and plan accordingly before migration.</p>
 
 <p>Apache Geronimo includes a Web application container supporting J2EE Web applications. The Web container itself supports basic configuration such as network ports and SSL options, and each Web application may include Geronimo-specific configuration information as well. Web applications participate in the Geronimo security infrastructure, so authenticating to a Web application allows access to secure EJBs and Connectors as well.</p>
 
-<p>Apache Geronimo currently supports two Web containers: <b>Jetty</b> and <b>Tomcat</b>.</p>
+<p>Apache Geronimo currently supports two Web containers: <strong>Jetty</strong> and <strong>Tomcat</strong>.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Jetty"></a>Jetty</h3>
+<h3 id="JBosstoGeronimo-ServletsandJSPsMigration-Jetty">Jetty</h3>
 <p>Jetty is a 100% Java HTTP Server and Servlet Container. This means that you do not need to configure and run a separate Web server in order to use servlets and JSPs to generate dynamic content. Jetty is a fully featured Web server for static and dynamic content.</p>
 
 <p>Unlike separate server/container solutions, Jetty's Web server and Web application run in the same process without interconnection overheads and complications.  Furthermore, as a pure java component, Jetty can be easily included in your application for demonstration, distribution or deployment. Jetty is available on all Java supported platforms.</p>
@@ -123,14 +123,14 @@ This article will help you migrate servl
 
 <p>Each Jetty connector is a GBean, so the process of configuring a Jetty connector involves configuring a GBean.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-ApacheTomcat"></a>Apache Tomcat</h3>
+<h3 id="JBosstoGeronimo-ServletsandJSPsMigration-ApacheTomcat">Apache Tomcat</h3>
 <p>Apache Tomcat is the servlet container that is used in the official Reference Implementation for the Java Servlet and JavaServer Pages technologies.</p>
 
 <p><a shape="rect" class="external-link" href="http://java.sun.com/products/servlet" rel="nofollow">http://java.sun.com/products/servlet</a><br clear="none">
 <a shape="rect" class="external-link" href="http://java.sun.com/products/jsp" rel="nofollow">http://java.sun.com/products/jsp</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Thedifferences"></a>The differences</h2>
-<p>JBoss v4 supports only Tomcat 5.5, which is the default Web container. The embedded Tomcat service is the expanded SAR <b>jbossweb-tomcat55.sar</b> in the deploy directory. The web.xml file that provides a default configuration set for Web application is also found in this exapanded SAR directory structure. </p>
+<h2 id="JBosstoGeronimo-ServletsandJSPsMigration-Thedifferences">The differences</h2>
+<p>JBoss v4 supports only Tomcat 5.5, which is the default Web container. The embedded Tomcat service is the expanded SAR <strong>jbossweb-tomcat55.sar</strong> in the deploy directory. The web.xml file that provides a default configuration set for Web application is also found in this exapanded SAR directory structure. </p>
 
 <p>The HTTP connector is set up on port 8080 and port 8009 is used if you want to connect via a separate Web server such as Apache HTTP.</p>
 
@@ -138,39 +138,37 @@ This article will help you migrate servl
 
 <p>For very simple Web applications with no security nor resource references, a Geronimo deployment plan is not required, a default context root and dependencies will be provided automatically at deployment time.</p>
 
-<p>The Geronimo Web application deployment plan is <b>geronimo-web.xml</b>. The corresponding deployment descriptor in Jboss is <b>jboss-web.xml</b>. For further details on Geronimo deployment architecture you may refer to the <a shape="rect" class="external-link" href="http://www.ibm.com/developerworks/library/os-ag-deploy" rel="nofollow">Understand Geronimo's deployment architecture</a> article.</p>
+<p>The Geronimo Web application deployment plan is <strong>geronimo-web.xml</strong>. The corresponding deployment descriptor in Jboss is <strong>jboss-web.xml</strong>. For further details on Geronimo deployment architecture you may refer to the <a shape="rect" class="external-link" href="http://www.ibm.com/developerworks/library/os-ag-deploy" rel="nofollow">Understand Geronimo's deployment architecture</a> article.</p>
 
-<p>Another difference with servlets and JSPs lies in the way the Web application is deployed. In Geronimo, the application package (ear, war, rar or jar) is deployed using the deployment tool <b>deployer.jar</b> located in the &lt;geronimo_home&gt;/bin directory.<br clear="none">
-<a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-deploymentTool"></a><br clear="none">
+<p>Another difference with servlets and JSPs lies in the way the Web application is deployed. In Geronimo, the application package (ear, war, rar or jar) is deployed using the deployment tool <strong>deployer.jar</strong> located in the &lt;geronimo_home&gt;/bin directory.<br clear="none">
+<span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-deploymentTool"></span><br clear="none">
 The deployer.jar deploys the application module based on the information provided in the deployment plan (if a plan is provided) to the Geronimo server. The server then saves the metadata to a configuration store and the executables to a binary repository. The following figure illustrates the behavior of the deployment tool.</p>
 
-<p><span class="image-wrap" style=""><img src="jboss-to-geronimo-servlets-and-jsps-migration.data/deployer.jpg" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image" src="https://cwiki.apache.org/confluence/download/attachments/65031/deployer.jpg?version=1&amp;modificationDate=1188481074000&amp;api=v2" data-image-src="/confluence/download/attachments/65031/deployer.jpg?version=1&amp;modificationDate=1188481074000&amp;api=v2"></p>
 
 <p>In JBoss, a Web application is deployed by simply copying the application package (ear, war, rar or jar) into the &lt;jboss_home&gt;/server/&lt;your_server_name&gt;/deploy directory from where the server detects its presence and deploys it accordingly.</p>
 
 <p>The following table summarizes the differences between JBoss and Geronimo.</p>
 
-<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Feature</th><th colspan="1" rowspan="1" class="confluenceTh">JBoss v4</th><th colspan="1" rowspan="1" class="confluenceTh">Apache Geronimo</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Deployment descriptor/plan</td><td colspan="1" rowspan="1" class="confluenceTd">jboss.xml</td><td colspan="1" rowspan="1" class="confluenceTd">geronimo-web.xml</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Method of deployment</td><td colspan="1" rowspan="1" class="confluenceTd">Copy the package (ear, war, rar or jar) to the deploy folder of the JBoss server &lt;jboss_home&gt;/server/&lt;your_server_name&gt;/deploy</td><td colspan="1" rowspan="1" class="confluenceTd"><a shape="rect" href="deployer-tool.html" title="Deployer tool">Deployer tool</a> available in server's bin directory<br clear="none">
-&lt;geronimo_home&gt;/bin. Deployment is also available through the <a shape="rect" href="geronimo-administration-console.html" title="Geronimo Administration Console">Geronimo Administration Console</a>. A third option is <span class="error">[Hot deployment]</span>, which would be the equivalent to JBoss functionality.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Web container</td><td colspan="1" rowspan="1" class="confluenceTd">Apache Tomcat 5.5</td><td colspan="1" rowspan="1" class="confluenceTd">Jetty and/or Apache Tomcat</td></tr></tbody></table>
-</div>
+<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Feature</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>JBoss v4</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Apache Geronimo</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Deployment descriptor/plan</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>jboss.xml</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>geronimo-web.xml</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Method of deployment</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Copy the package (ear, war, rar or jar) to the deploy folder of the JBoss server &lt;jboss_home&gt;/server/&lt;your_server_name&gt;/deploy</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" href="deployer-tool.html">Deployer tool</a> available in server's bin directory<br clear="none">
+&lt;geronimo_home&gt;/bin. Deployment is also available through the <a shape="rect" href="geronimo-administration-console.html">Geronimo Administration Console</a>. A third option is <a shape="rect" class="unresolved" href="#">Hot deployment</a>, which would be the equivalent to JBoss functionality.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Web container</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Apache Tomcat 5.5</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Jetty and/or Apache Tomcat</p></td></tr></tbody></table></div>
 
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Sampleapplication"></a>Sample application <a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-sampleApp"></a></h1>
-<p>The <a shape="rect" href="jboss-to-geronimo-servlets-and-jsps-migration.data/college_fest.zip?version=3&amp;modificationDate=1188483435000">College Fest</a> application handles registration for events at a college festival. This is a very simple application that does not use any type of database. The College Fest application has the following four pages:</p>
+<h1 id="JBosstoGeronimo-ServletsandJSPsMigration-SampleapplicationsampleApp">Sample application <span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-sampleApp"></span></h1>
+<p>The <a shape="rect" href="jboss-to-geronimo-servlets-and-jsps-migration.data/college_fest.zip?version=3&amp;modificationDate=1188483435000&amp;api=v2">College Fest</a> application handles registration for events at a college festival. This is a very simple application that does not use any type of database. The College Fest application has the following four pages:</p>
 
 <ul><li>Welcome page</li><li>Event List page</li><li>Event Details page</li><li>Registration page</li></ul>
 
 
 <p>The following figure illustrates the application flow:</p>
 
-<p><span class="image-wrap" style=""><img src="jboss-to-geronimo-servlets-and-jsps-migration.data/webApp_flow.jpg" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image" src="https://cwiki.apache.org/confluence/download/attachments/65031/webApp_flow.jpg?version=1&amp;modificationDate=1188481062000&amp;api=v2" data-image-src="/confluence/download/attachments/65031/webApp_flow.jpg?version=1&amp;modificationDate=1188481062000&amp;api=v2"></p>
 
 <p>The user access the Welcome page and enters user name and college. From there the user can see the list of available events. The user can access the details for each Event by clicking them from the list. From the Event details page the user can register for that particular event. </p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-ApplicationclassesandJSPpages"></a>Application classes and JSP pages</h2>
+<h2 id="JBosstoGeronimo-ServletsandJSPsMigration-ApplicationclassesandJSPpages">Application classes and JSP pages</h2>
 <p>The College Fest sample application consists of the following two servlets:</p>
 <ul><li>WelcomeServlet - Handles user login and then grabs the user name and dispatches this to the next servlet.</li><li>PersonalServlet - Personalizes the page for the user and hands over control to welcome.jsp.</li></ul>
 
@@ -179,41 +177,41 @@ The deployer.jar deploys the application
 <ul><li>welcome.jsp - Displays the events list to the user so that s/he can choose on what event to register.</li><li>dc.jsp - Displays the details for the Dumb Charades event.</li><li>pp.jsp - Displays the details for the Pot Potpourri event.</li><li>wtgw.jsp - Displays the details for the  What's The Good Word event.</li><li>gq.jsp - Displays the details for the General Quiz event.</li><li>team_reg.jsp - Handles the user registration for one event.</li></ul>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Toolsused"></a>Tools used</h2>
+<h2 id="JBosstoGeronimo-ServletsandJSPsMigration-Toolsused">Tools used</h2>
 <p>The tools used for developing and building the College Fest sample application are:</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Eclipse"></a>Eclipse</h3>
+<h3 id="JBosstoGeronimo-ServletsandJSPsMigration-Eclipse">Eclipse</h3>
 <p>The Eclipse IDE was used for development of the sample application. This is a very powerful and popular open source development tool. Integration plug-ins are available for both JBoss and Geronimo. Eclipse can be downloaded from the following URL:<br clear="none">
 <a shape="rect" class="external-link" href="http://www.eclipse.org" rel="nofollow">http://www.eclipse.org</a></p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-ApacheAnt"></a>Apache Ant</h3>
+<h3 id="JBosstoGeronimo-ServletsandJSPsMigration-ApacheAnt">Apache Ant</h3>
 <p>Ant is a pure Java build tool. It is used for building the war files for the College Fest application. Ant can be downloaded from the following URL:<br clear="none">
 <a shape="rect" class="external-link" href="http://ant.apache.org">http://ant.apache.org</a></p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-TheJBossenvironment"></a>The JBoss environment <a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-JBoss"></a></h1>
+<h1 id="JBosstoGeronimo-ServletsandJSPsMigration-TheJBossenvironmentJBoss">The JBoss environment <span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-JBoss"></span></h1>
 <p>This section shows you how and where the sample JBoss reference environment was installed so you can map this scenario to your own implementation.</p>
 
 <p>Detailed instructions for installing, configuring, and managing JBoss are provided in the product documentation. Check the product Web site for the most updated documents.</p>
 
 <p>The following list highlights the general tasks you will need to complete to install and configure the initial environment as the starting point for deploying the sample application.</p>
 
-<ol><li>Download and install JBoss v4 as explained in the product documentation guides. From now on the installation directory will be referred as <b>&lt;jboss_home&gt;</b></li><li>Create a copy of the default JBoss v4 application server. Copy recursively <b>&lt;jboss_home&gt;\server\default</b> to <b>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;</b></li><li>Start the new server by running the <tt>run.sh -c &lt;your_server_name&gt;</tt> command from the <b>&lt;jboss_home&gt;\bin</b> directory.</li><li>Once the server is started, you can verify that it is running by opening a Web browser and pointing it to this URL: <a shape="rect" class="external-link" href="http://localhost:8080" rel="nofollow">http://localhost:8080</a>. You should see the JBoss Welcome window and be able to access the JBoss console.</li><li>Once the application server is up and running, the next step is to install and configure all the remaining prerequisite software required by the sample application. This s
 tep is described in the following section.</li></ol>
+<ol><li>Download and install JBoss v4 as explained in the product documentation guides. From now on the installation directory will be referred as <strong>&lt;jboss_home&gt;</strong></li><li>Create a copy of the default JBoss v4 application server. Copy recursively <strong>&lt;jboss_home&gt;\server\default</strong> to <strong>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;</strong></li><li>Start the new server by running the <code>run.sh -c &lt;your_server_name&gt;</code> command from the <strong>&lt;jboss_home&gt;\bin</strong> directory.</li><li>Once the server is started, you can verify that it is running by opening a Web browser and pointing it to this URL: <a shape="rect" class="external-link" href="http://localhost:8080" rel="nofollow">http://localhost:8080</a>. You should see the JBoss Welcome window and be able to access the JBoss console.</li><li>Once the application server is up and running, the next step is to install and configure all the remaining prerequisite softwar
 e required by the sample application. This step is described in the following section.</li></ol>
 
 
-<p>As mentioned before, Apache Ant is used to build the binaries for the College Fest application. If you do not have Ant installed this is a good time for doing it and make sure that <b>&lt;ant_home&gt;\bin</b> directory is added to the system's path variable.</p>
+<p>As mentioned before, Apache Ant is used to build the binaries for the College Fest application. If you do not have Ant installed this is a good time for doing it and make sure that <strong>&lt;ant_home&gt;\bin</strong> directory is added to the system's path variable.</p>
 
 <p>Apache Ant can be downloaded from the following URL:</p>
 
 <p><a shape="rect" class="external-link" href="http://ant.apache.org">http://ant.apache.org</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Buildthesampleapplication"></a>Build the sample application</h2>
+<h2 id="JBosstoGeronimo-ServletsandJSPsMigration-Buildthesampleapplication">Build the sample application</h2>
 <p>The College Fest application included with this article provides an Ant script that you will use in order to build the application. Download the College Fest application from the following link:</p>
 
-<p><a shape="rect" href="jboss-to-geronimo-servlets-and-jsps-migration.data/college_fest.zip?version=3&amp;modificationDate=1188483435000">College Fest</a></p>
+<p><a shape="rect" href="jboss-to-geronimo-servlets-and-jsps-migration.data/college_fest.zip?version=3&amp;modificationDate=1188483435000&amp;api=v2">College Fest</a></p>
 
-<p>After extracting the zip file, a college_fest directory is created. In that directory open the <b>build.properties</b> file and edit the properties to match your environment as shown in the following example:</p>
+<p>After extracting the zip file, a college_fest directory is created. In that directory open the <strong>build.properties</strong> file and edit the properties to match your environment as shown in the following example:</p>
 
 <div class="preformatted panel" style="border-style: solid;border-width: 1px;"><div class="preformattedHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Update the build.properties file</b></div><div class="preformattedContent panelContent">
 <pre>#Replace java.home with your jdk directory
@@ -227,63 +225,63 @@ geronimo.home=&lt;geronimo_home&gt;
 </pre>
 </div></div>
 
-<p>In the college_fest directory you can also find two build files, build.xml and jboss-build.xml. build.xml is the default build file so if you just type <b>ant</b>  this file will be used for building the application. For this particular sample application the jboss-build.xml file is provided.</p>
+<p>In the college_fest directory you can also find two build files, build.xml and jboss-build.xml. build.xml is the default build file so if you just type <strong>ant</strong>  this file will be used for building the application. For this particular sample application the jboss-build.xml file is provided.</p>
 
 <p>From a command line, still within the college_fest directory type the following command:</p>
 
-<p><b>ant -f jboss-build.xml clean deploy</b></p>
+<p><strong>ant -f jboss-build.xml clean deploy</strong></p>
 
-<p>With this command, ant will use the targets defined in the jboss-build.xml file to build the College Fest application and deploy it to the JBoss server. Take a special look at <b>&lt;target name="deploy" ...&gt;</b>, here is where the jboss-build.xml tell ant where to deploy the WAR file. The following example shows the definitions in the jboss-build.xml file.</p>
+<p>With this command, ant will use the targets defined in the jboss-build.xml file to build the College Fest application and deploy it to the JBoss server. Take a special look at <strong>&lt;target name="deploy" ...&gt;</strong>, here is where the jboss-build.xml tell ant where to deploy the WAR file. The following example shows the definitions in the jboss-build.xml file.</p>
 
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>jboss-build.xml</b></div><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>jboss-build.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0"?&gt;
+&lt;?xml version=&quot;1.0&quot;?&gt;
 &lt;!-- build file for building a war --&gt;
 
-&lt;project name="build" default="war" basedir="."&gt;
+&lt;project name=&quot;build&quot; default=&quot;war&quot; basedir=&quot;.&quot;&gt;
 
-    &lt;property file="build.properties"/&gt;
-    &lt;property name="src.dir" value="src"/&gt;
-    &lt;property name="dest.dir" value="bin"/&gt;
+    &lt;property file=&quot;build.properties&quot;/&gt;
+    &lt;property name=&quot;src.dir&quot; value=&quot;src&quot;/&gt;
+    &lt;property name=&quot;dest.dir&quot; value=&quot;bin&quot;/&gt;
     
-    &lt;target name="clean" description="Delete all generated files"&gt;
-        &lt;echo message="Deleting bin directory" /&gt;
-        &lt;delete dir="bin" /&gt;
+    &lt;target name=&quot;clean&quot; description=&quot;Delete all generated files&quot;&gt;
+        &lt;echo message=&quot;Deleting bin directory&quot; /&gt;
+        &lt;delete dir=&quot;bin&quot; /&gt;
     &lt;/target&gt;
 
-	&lt;target name="compile"&gt;
-		&lt;mkdir dir="${dest.dir}"/&gt;
-		&lt;javac srcdir="${src.dir}" destdir="${dest.dir}"&gt;
-			&lt;classpath path="${java.home}/lib/tools.jar"/&gt;
-			&lt;classpath path="${j2ee.home}/lib/j2ee.jar"/&gt;
+	&lt;target name=&quot;compile&quot;&gt;
+		&lt;mkdir dir=&quot;${dest.dir}&quot;/&gt;
+		&lt;javac srcdir=&quot;${src.dir}&quot; destdir=&quot;${dest.dir}&quot;&gt;
+			&lt;classpath path=&quot;${java.home}/lib/tools.jar&quot;/&gt;
+			&lt;classpath path=&quot;${j2ee.home}/lib/j2ee.jar&quot;/&gt;
 		&lt;/javac&gt;
 	&lt;/target&gt;
 
-	&lt;target name="war" depends="compile"&gt;
-		&lt;war destfile="college_fest.war" webxml="WEB-INF/web.xml"&gt;
-			&lt;zipfileset dir="jsp" prefix="jsp"/&gt;   	 
-			&lt;zipfileset dir="pix" prefix="pix"/&gt;   	 
-			&lt;classes dir="${dest.dir}"/&gt;   
-                        &lt;webinf dir="WEB-INF" /&gt;
+	&lt;target name=&quot;war&quot; depends=&quot;compile&quot;&gt;
+		&lt;war destfile=&quot;college_fest.war&quot; webxml=&quot;WEB-INF/web.xml&quot;&gt;
+			&lt;zipfileset dir=&quot;jsp&quot; prefix=&quot;jsp&quot;/&gt;   	 
+			&lt;zipfileset dir=&quot;pix&quot; prefix=&quot;pix&quot;/&gt;   	 
+			&lt;classes dir=&quot;${dest.dir}&quot;/&gt;   
+                        &lt;webinf dir=&quot;WEB-INF&quot; /&gt;
 		&lt;/war&gt;
 	&lt;/target&gt;
 
-	&lt;target name="deploy" depends="war"&gt;
-		&lt;copy file="college_fest.war" todir="${jboss.server}/deploy"/&gt;
+	&lt;target name=&quot;deploy&quot; depends=&quot;war&quot;&gt;
+		&lt;copy file=&quot;college_fest.war&quot; todir=&quot;${jboss.server}/deploy&quot;/&gt;
 	&lt;/target&gt;
 
-	&lt;target name="undeploy"&gt;
-		&lt;delete file="${jboss.server}/deploy/college_fest.war"/&gt;
+	&lt;target name=&quot;undeploy&quot;&gt;
+		&lt;delete file=&quot;${jboss.server}/deploy/college_fest.war&quot;/&gt;
     &lt;/target&gt;
 &lt;/project&gt;
 ]]></script>
 </div></div>
 
-<p>The war created by the ant build contains a JBoss specific deployment descriptor, the <b>jboss-web.xml</b> file in the WEB-INF directory of the WAR is shown in the following example.</p>
+<p>The war created by the ant build contains a JBoss specific deployment descriptor, the <strong>jboss-web.xml</strong> file in the WEB-INF directory of the WAR is shown in the following example.</p>
 
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>JBoss deployment descriptor</b></div><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>JBoss deployment descriptor</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 
 &lt;jboss-web&gt;
 
@@ -296,8 +294,8 @@ geronimo.home=&lt;geronimo_home&gt;
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Deploythesampleapplication"></a>Deploy the sample application</h2>
-<p>The previous step showed how to deploy the application at build time by specifying a customized jboss-build.xml file. If you used the default build.xml file at build time you still need to deploy the College Fest application manually. To deploy the College Fest application in JBoss, copy the <b>college_fest.war</b> file you just built with Ant to the following directory:</p>
+<h2 id="JBosstoGeronimo-ServletsandJSPsMigration-Deploythesampleapplication">Deploy the sample application</h2>
+<p>The previous step showed how to deploy the application at build time by specifying a customized jboss-build.xml file. If you used the default build.xml file at build time you still need to deploy the College Fest application manually. To deploy the College Fest application in JBoss, copy the <strong>college_fest.war</strong> file you just built with Ant to the following directory:</p>
 
 <p>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\deploy</p>
 
@@ -305,7 +303,7 @@ geronimo.home=&lt;geronimo_home&gt;
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Testingtheapplication"></a>Testing the application <a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-test"></a></h2>
+<h2 id="JBosstoGeronimo-ServletsandJSPsMigration-Testingtheapplicationtest">Testing the application <span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-test"></span></h2>
 <p>To test the application, open a Web browser and access the following URL:</p>
 
 <p><a shape="rect" class="external-link" href="http://localhost:8080/college_fest" rel="nofollow">http://localhost:8080/college_fest</a></p>
@@ -314,28 +312,41 @@ geronimo.home=&lt;geronimo_home&gt;
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-TheGeronimoenvironment"></a>The Geronimo environment <a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Geronimo"></a></h1>
+<h1 id="JBosstoGeronimo-ServletsandJSPsMigration-TheGeronimoenvironmentGeronimo">The Geronimo environment <span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-Geronimo"></span></h1>
 <p>Download and install Geronimo from the following URL:</p>
 
 <p><a shape="rect" class="external-link" href="http://geronimo.apache.org/downloads.html">http://geronimo.apache.org/downloads.html</a></p>
 
-<p>The release notes available there provide clear instructions on system requirements and how to install and start Geronimo.  Throughout the rest of this article we will refer to the Geronimo installation directory as <b>&lt;geronimo_home&gt;</b>.</p>
+<p>The release notes available there provide clear instructions on system requirements and how to install and start Geronimo.  Throughout the rest of this article we will refer to the Geronimo installation directory as <strong>&lt;geronimo_home&gt;</strong>.</p>
+
+    <div class="aui-message problem shadowed information-macro">
+                    <p class="title">TCP/IP ports conflict</p>
+                            <span class="aui-icon icon-problem">Icon</span>
+                <div class="message-content">
+                            <p>If you are planning to run JBoss and Geronimo on the same machine consider to change the default service ports on, at least, one of these servers.</p>
+                    </div>
+    </div>
 
-<div class="panelMacro"><table class="warningMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/forbidden.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1"><b>TCP/IP ports conflict</b><br clear="none">If you are planning to run JBoss and Geronimo on the same machine consider to change the default service ports on, at least, one of these servers.</td></tr></table></div>
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Stepbystepmigration"></a>Step-by-step migration <a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-migration"></a></h1>
-<p>In order to migrate the College Fest application to Geronimo you need to replace the jboss-web.xml file with a <b>geronimo-web.xml</b> file which is the Geronimo specific descriptor file. The geronimo-web.xml file is located in the WEB-INF directory withing the college_fest directory structure. The Geronimo deployment plan geronimo-web.xml is illustrated in the following example.</p>
+<h1 id="JBosstoGeronimo-ServletsandJSPsMigration-Step-by-stepmigrationmigration">Step-by-step migration <span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-migration"></span></h1>
+<p>In order to migrate the College Fest application to Geronimo you need to replace the jboss-web.xml file with a <strong>geronimo-web.xml</strong> file which is the Geronimo specific descriptor file. The geronimo-web.xml file is located in the WEB-INF directory withing the college_fest directory structure. The Geronimo deployment plan geronimo-web.xml is illustrated in the following example.</p>
+
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>The following geronimo-web.xml was generated using the J2G tool.</p>
+                    </div>
+    </div>
 
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">The following geronimo-web.xml was generated using the J2G tool.</td></tr></table></div>
 
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Geronimo specific deployment plan geronimo-web.xml</b></div><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>Geronimo specific deployment plan geronimo-web.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1" 
-         xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1" 
-         xmlns:security="http://geronimo.apache.org/xml/ns/security-1.1" 
-         xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.1"&gt;
+&lt;web-app xmlns=&quot;http://geronimo.apache.org/xml/ns/j2ee/web-1.1&quot; 
+         xmlns:naming=&quot;http://geronimo.apache.org/xml/ns/naming-1.1&quot; 
+         xmlns:security=&quot;http://geronimo.apache.org/xml/ns/security-1.1&quot; 
+         xmlns:sys=&quot;http://geronimo.apache.org/xml/ns/deployment-1.1&quot;&gt;
   &lt;sys:environment&gt;
     &lt;sys:moduleId&gt;
       &lt;sys:groupId&gt;j2g&lt;/sys:groupId&gt;
@@ -350,45 +361,45 @@ geronimo.home=&lt;geronimo_home&gt;
 ]]></script>
 </div></div>
 
-<p>Given that College Fest is a very simple application, the Geronimo deployment plan will also be very simple. Remember that this application does not use any database access nor has security configured. While reading other articles in the <b>JBoss to Geronimo</b> migration series, you will notice how the complexity of the deployment plan increases as the sample applications for the different migration scenarios also grow in complexity.</p>
+<p>Given that College Fest is a very simple application, the Geronimo deployment plan will also be very simple. Remember that this application does not use any database access nor has security configured. While reading other articles in the <strong>JBoss to Geronimo</strong> migration series, you will notice how the complexity of the deployment plan increases as the sample applications for the different migration scenarios also grow in complexity.</p>
 
 <p>Earlier in this article it was discussed the behavior of the <a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-deploymentTool">deployment tool</a>. During the deployment process, you provide to the deployment tool the application module and a deployment plan. The College Fest sample application is so simple that you may choose not to provide any deployment plan and let Geronimo do the deployment with a default set of values (a default context root for example).</p>
 
 <p>Last time you built the College Fest sample application it was configured for ant to use the jboss-build.xml file instead of the default build.xml. The following example shows the content of the default build.xml file.</p>
 
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>build.xml</b></div><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>build.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0"?&gt;
+&lt;?xml version=&quot;1.0&quot;?&gt;
 &lt;!-- build file for building a war --&gt;
 
-&lt;project name="build" default="war" basedir="."&gt;
+&lt;project name=&quot;build&quot; default=&quot;war&quot; basedir=&quot;.&quot;&gt;
 
-    &lt;property file="build.properties"/&gt;
-    &lt;property name="src.dir" value="src"/&gt;
-    &lt;property name="dest.dir" value="bin"/&gt;
+    &lt;property file=&quot;build.properties&quot;/&gt;
+    &lt;property name=&quot;src.dir&quot; value=&quot;src&quot;/&gt;
+    &lt;property name=&quot;dest.dir&quot; value=&quot;bin&quot;/&gt;
 
 
-    &lt;target name="clean" description="Delete all generated files."&gt;
-        &lt;echo message="Deleting bin folder" /&gt;
-        &lt;delete dir="bin"/&gt;
+    &lt;target name=&quot;clean&quot; description=&quot;Delete all generated files.&quot;&gt;
+        &lt;echo message=&quot;Deleting bin folder&quot; /&gt;
+        &lt;delete dir=&quot;bin&quot;/&gt;
     &lt;/target&gt;
 
-      &lt;target name="compile"&gt;
-    	&lt;mkdir dir="${dest.dir}"/&gt;
+      &lt;target name=&quot;compile&quot;&gt;
+    	&lt;mkdir dir=&quot;${dest.dir}&quot;/&gt;
 
-        &lt;javac srcdir="${src.dir}" destdir="${dest.dir}"&gt;
-            &lt;classpath path="${java.home}/lib/tools.jar"/&gt;
-            &lt;!--classpath path="${j2ee.home}/lib/j2ee.jar"/--&gt;
-            &lt;classpath path="${geronimo.home}/repository/org/apache/geronimo/specs/geronimo-servlet_2.5_spec/1.1/geronimo-servlet_2.5_spec-1.1.jar" /&gt;
+        &lt;javac srcdir=&quot;${src.dir}&quot; destdir=&quot;${dest.dir}&quot;&gt;
+            &lt;classpath path=&quot;${java.home}/lib/tools.jar&quot;/&gt;
+            &lt;!--classpath path=&quot;${j2ee.home}/lib/j2ee.jar&quot;/--&gt;
+            &lt;classpath path=&quot;${geronimo.home}/repository/org/apache/geronimo/specs/geronimo-servlet_2.5_spec/1.1/geronimo-servlet_2.5_spec-1.1.jar&quot; /&gt;
         &lt;/javac&gt;
     &lt;/target&gt;
 
-    &lt;target name="war" depends="compile"&gt;
-        &lt;war destfile="college_fest.war" webxml="WEB-INF/web.xml"&gt;
-            &lt;zipfileset dir="jsp" prefix="jsp"/&gt;
-            &lt;zipfileset dir="pix" prefix="pix"/&gt;   	    
-            &lt;classes dir="${dest.dir}"/&gt;    
-            &lt;webinf dir="WEB-INF" /&gt;
+    &lt;target name=&quot;war&quot; depends=&quot;compile&quot;&gt;
+        &lt;war destfile=&quot;college_fest.war&quot; webxml=&quot;WEB-INF/web.xml&quot;&gt;
+            &lt;zipfileset dir=&quot;jsp&quot; prefix=&quot;jsp&quot;/&gt;
+            &lt;zipfileset dir=&quot;pix&quot; prefix=&quot;pix&quot;/&gt;   	    
+            &lt;classes dir=&quot;${dest.dir}&quot;/&gt;    
+            &lt;webinf dir=&quot;WEB-INF&quot; /&gt;
         &lt;/war&gt;
 &lt;/target&gt;
 
@@ -397,18 +408,18 @@ geronimo.home=&lt;geronimo_home&gt;
 ]]></script>
 </div></div>
 
-<p>To build the migrated application run <b>ant</b> from the command line without specifying any additional parameters, a college_fest.war file will be created in the root directory of the College Fest application directory structure.</p>
+<p>To build the migrated application run <strong>ant</strong> from the command line without specifying any additional parameters, a college_fest.war file will be created in the root directory of the College Fest application directory structure.</p>
 
-<p>To delete the generated files for a clean build run <b>ant clean</b> followed by an <b>ant.</b></p>
+<p>To delete the generated files for a clean build run <strong>ant clean</strong> followed by an <strong>ant.</strong></p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Deploythemigratedsampleapplication"></a>Deploy the migrated sample application</h2>
+<h2 id="JBosstoGeronimo-ServletsandJSPsMigration-Deploythemigratedsampleapplication">Deploy the migrated sample application</h2>
 <p>To deploy the migrated College Fest application, make sure the Geronimo server is up and running. </p>
 
-<p>From a command line, change directory to <b><tt>&lt;geronimo_home&gt;/bin</tt></b> and type the following command:</p>
+<p>From a command line, change directory to <strong><code>&lt;geronimo_home&gt;/bin</code></strong> and type the following command:</p>
 
-<p><tt>deploy --user system --password manager deploy &lt;college_fest_home&gt;/college_fest.war</tt></p>
+<p><code>deploy --user system --password manager deploy &lt;college_fest_home&gt;/college_fest.war</code></p>
 
 <p>Once the application is deployed, open a Web browser and access the following URL:</p>
 
@@ -418,12 +429,11 @@ geronimo.home=&lt;geronimo_home&gt;
 
 <p><a shape="rect" href="#JBosstoGeronimo-ServletsandJSPsMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-Summary"></a>Summary <a shape="rect" name="JBosstoGeronimo-ServletsandJSPsMigration-summary"></a></h1>
+<h1 id="JBosstoGeronimo-ServletsandJSPsMigration-Summarysummary">Summary <span class="confluence-anchor-link" id="JBosstoGeronimo-ServletsandJSPsMigration-summary"></span></h1>
 <p>This article has shown you how to migrate a simple Servlet and JSPs application, from JBoss to the Apache Geronimo application server. You followed step-by-step instructions to build the application, deploy and run it, and then migrate it to the Geronimo environment.</p>
 
 <p>Some remarks after reading this article:</p>
-<ul><li>Apache Geronimo provides two different Web containers, Jetty and Apache Tomcat.</li><li>You learnt how to use the deployer too for deploying an application in Geronimo.</li><li>Not always a Geronimo deployment plan is needed, if the application does not use resource references you can accept the deployment defaults from Geronimo.</li></ul>
-</div>
+<ul><li>Apache Geronimo provides two different Web containers, Jetty and Apache Tomcat.</li><li>You learnt how to use the deployer too for deploying an application in Geronimo.</li><li>Not always a Geronimo deployment plan is needed, if the application does not use resource references you can accept the deployment defaults from Geronimo.</li></ul></div>
         </div>
 
         

Modified: websites/production/geronimo/content/GMOxDOC20/jms-and-mdb-sample-application.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/jms-and-mdb-sample-application.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/jms-and-mdb-sample-application.html Tue Jul 29 00:52:18 2014
@@ -23,6 +23,7 @@
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shCore.js' type='text/javascript'></script>
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
+  <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushPlain.js' type='text/javascript'></script>
   
   <script type="text/javascript">
   SyntaxHighlighter.defaults['toolbar'] = false;
@@ -95,16 +96,31 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><style type="text/css">/*<![CDATA[*/
-table.ScrollbarTable  {border: none;padding: 3px;width: 100%;padding: 3px;margin: 0px;background-color: #f0f0f0}
-table.ScrollbarTable td.ScrollbarPrevIcon {text-align: center;width: 16px;border: none;}
-table.ScrollbarTable td.ScrollbarPrevName {text-align: left;border: none;}
-table.ScrollbarTable td.ScrollbarParent {text-align: center;border: none;}
-table.ScrollbarTable td.ScrollbarNextName {text-align: right;border: none;}
-table.ScrollbarTable td.ScrollbarNextIcon {text-align: center;width: 16px;border: none;}
+          <div class="wiki-content maincontent">    
+<div class="atb-scrollbar-macro">
+    <div class="prev">
+        <a shape="rect" href="inbound-jca-example.html" rel="prev">
+                                    <span class="aui-icon aui-icon-small atb-icon-arrow-left">Previous</span>
+                                <span class="title">Inbound JCA example</span>
+            </a>
 
-/*]]>*/</style><div class="Scrollbar"><table class="ScrollbarTable"><tr><td colspan="1" rowspan="1" class="ScrollbarPrevIcon"><a shape="rect" href="inbound-jca-example.html"><img align="middle" border="0" src="https://cwiki.apache.org/confluence/images/icons/back_16.gif" width="16" height="16"></a></td><td colspan="1" rowspan="1" class="ScrollbarPrevName" width="33%"><a shape="rect" href="inbound-jca-example.html">Inbound JCA example</a>&#160;</td><td colspan="1" rowspan="1" class="ScrollbarParent" width="33%"><sup><a shape="rect" href="sample-applications.html"><img align="middle" border="0" src="https://cwiki.apache.org/confluence/images/icons/up_16.gif" width="8" height="8"></a></sup><a shape="rect" href="sample-applications.html">Sample applications</a></td><td colspan="1" rowspan="1" class="ScrollbarNextName" width="33%">&#160;<a shape="rect" href="jms-resources-deployment.html">JMS Resources deployment</a></td><td colspan="1" rowspan="1" class="ScrollbarNextIcon"><a shape="rec
 t" href="jms-resources-deployment.html"><img align="middle" border="0" src="https://cwiki.apache.org/confluence/images/icons/forwd_16.gif" width="16" height="16"></a></td></tr></table></div>
-<p><a shape="rect" name="JMSandMDBsampleapplication-top"></a><br clear="none">
+    </div>
+    <div class="parent">
+                    <a shape="rect" href="sample-applications.html" rel="parent">
+                                            <span class="aui-icon aui-icon-small atb-icon-arrow-up">Up</span>
+                                        <span class="title">Sample applications</span>
+                </a>
+
+            </div>
+    <div class="next">
+        <a shape="rect" href="jms-resources-deployment.html" rel="next">
+                <span class="title">JMS Resources deployment</span>
+                                    <span class="aui-icon aui-icon-small atb-icon-arrow-right">Next</span>
+                            </a>
+
+    </div>
+</div>
+<p><span class="confluence-anchor-link" id="JMSandMDBsampleapplication-top"></span><br clear="none">
 Enterprise messaging has become an increasingly important component of loosely coupled, reliable enterprise frameworks. This is due in large part to the proliferation of enterprise applications and disparate enterprise resources, and the increasing need to integrate these applications into cohesive systems. Over the years Messaging and Message Oriented Middleware (MOM) has provided this integration proprietary manner. Introduction of Java Messaging Service (JMS) as a standard, eliminated many of the disadvantages in proprietary MOM based products. In addition,Message Driven Beans(MDBs) introduced together with Enterprise Java Beans 2.0 have served to get the best out of existing investments in J2EE application servers. Most of the J2EE application servers in modern era are acting as a MOM with a whole lot of value added services to JMS. As a J2EE 1.4 certified application server, Apache Geronimo comes into the party with support of JMS integrating with one of the best breed open sou
 rce messaging frameworks, ActiveMQ. This article will provide you with a way to use JMS for your enterprise application scenario both as a local and remotely referred environments with Geronimo and ActiveMQ.</p>
 
 <p>The company referred in this sample application sells one specific item in both retail and wholesale markets under different categories. All the placed orders in the application have to be authorized by a company sales employee before delivering goods to the customer. For the wholesale market, the company has placed their agents all over the country. They send their orders as a bunch at once, which is called a consignment. End users place their orders using the company web site while agents send their consignments with a special software installed in their premises. All the consignments must be approved by the company General Manager before it is handed over to a sales employee.</p>
@@ -117,22 +133,22 @@ Enterprise messaging has become an incre
 <ul><li>Overview of JMS in Geronimo/ActiveMQ Enviroment</li><li>Application Overview</li><li>Configuring, Building and Deploying the Sample Application</li><li>Testing of the Sample Application</li><li>Summary</li></ul>
 
 
-<h1><a shape="rect" name="JMSandMDBsampleapplication-OverviewofJMSinGeronimo%2FActiveMQEnviroment"></a>Overview of JMS in Geronimo/ActiveMQ Enviroment <a shape="rect" name="JMSandMDBsampleapplication-overview"></a></h1>
+<h1 id="JMSandMDBsampleapplication-OverviewofJMSinGeronimo/ActiveMQEnviromentoverview">Overview of JMS in Geronimo/ActiveMQ Enviroment <span class="confluence-anchor-link" id="JMSandMDBsampleapplication-overview"></span></h1>
 
 <p>Geronimo server comes with a JMS server and application components that can access JMS resources like connection factories, topics and queues from it. This JMS server is also known as message broker. The default message broker supported by Geronimo is ActiveMQ, usually does not need to be changed since it is a mature and feature-rich JMS product. This implementation uses inbuilt Derby database for the message persistent features.</p>
 
 <p>ActiveMQ supports a large variety of transports (such as TCP, SSL, UDP, multicast, intra-JVM, and NIO) and client interactions (such as push, pull, and publish/subscribe). In the Geronimo context ActiveMQ supports MDBs, which are EJBs that consume JMS messages. It allows JMS applications to take J2EE specific features from Geronimo and application components such as JSPs, Servlets or EJBs utilizing JMS. Geronimo has implemented this JMS API in an abstract layer to support any JMS provider. It has achieved this feature by supporting J2EE Connector (JCA) specification. The JCA 1.5 specification details the contracts required between the application server and the driver supplied by ActiveMQ (resource adapter). Applications deployed in the Geronimo access ActiveMQ message broker only through this resource adapter(RA).</p>
 
-<h1><a shape="rect" name="JMSandMDBsampleapplication-ApplicationOverview"></a>Application Overview <a shape="rect" name="JMSandMDBsampleapplication-application"></a></h1>
+<h1 id="JMSandMDBsampleapplication-ApplicationOverviewapplication">Application Overview <span class="confluence-anchor-link" id="JMSandMDBsampleapplication-application"></span></h1>
 
 <p>Order processing application has two defined message queues to receive orders and consignments. Order requests can be generated and sent via the company's web application. When order requests are received to the order queue, a MDB will be triggered. It will carry out the next level of order request processing by saving those requests in to a server repository. Those saved order requests will be processed by a company employee later.</p>
 
 <p>The company's sales agents are using the consignment sender application to send consignment (collection of orders) requests from their locations. First, they will prepare consignment as an XML file, then it will be passed as an application parameter. Consignment sender application will read the content of an XML file (with a consignment request) and send it to the consignment queue. General Manager in the company uses the consignment receiver application to find out the consignment requests. When a consignment request received to the consignment queue, consignment receiver listener application will download those requests to the General Manager's computer. He will then authorize it and hand it over to a sales employee for further processing.</p>
 
-<h2><a shape="rect" name="JMSandMDBsampleapplication-Applicationcontents"></a>Application contents</h2>
+<h2 id="JMSandMDBsampleapplication-Applicationcontents">Application contents</h2>
 
 <p>The core of the order placement application will be deployed as an EAR to the application server. Overview of the contents of EAR is given in the following depiction.</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 |-Order.ear
    |- geronimo-activemq-ra-2.0-SNAPSHOT.rar
@@ -151,23 +167,23 @@ Enterprise messaging has become an incre
 ]]></script>
 </div></div>
 
-<h3><a shape="rect" name="JMSandMDBsampleapplication-MDBImplementation"></a>MDB Implementation</h3>
+<h3 id="JMSandMDBsampleapplication-MDBImplementation">MDB Implementation</h3>
 
 <p>The Message-Driven Bean uses the @MessageDriven annotation to replace the declaration of this MDB in the ejb-jar.xml file. By providing the annotation with further information it knows to look for a destination (in this case it happens to be a queue) to process. So this MDB will sit there and process messages passed into the 'OrderQueue.' The end result is that is echoes this message to the screen.</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>OrderRecvMDB.java</b></div><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>OrderRecvMDB.java</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 //
 // MessageDrivenBean that listens to items on the
-// 'OrderQueue' queue and processes them accordingly.
+// &#39;OrderQueue&#39; queue and processes them accordingly.
 //
 @MessageDriven(activationConfig = {
-    @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
-    @ActivationConfigProperty(propertyName="destination", propertyValue="OrderQueue")
+    @ActivationConfigProperty(propertyName=&quot;destinationType&quot;, propertyValue=&quot;javax.jms.Queue&quot;),
+    @ActivationConfigProperty(propertyName=&quot;destination&quot;, propertyValue=&quot;OrderQueue&quot;)
 })
 public class OrderRecvMDB implements MessageListener{
 
-    private static final String ORDER_MGMT_INFO = "order_mgmt.properties";
-    private static final String ORDER_REPO = "order.repo";
+    private static final String ORDER_MGMT_INFO = &quot;order_mgmt.properties&quot;;
+    private static final String ORDER_REPO = &quot;order.repo&quot;;
 
     public OrderRecvMDB() {
     }
@@ -175,7 +191,7 @@ public class OrderRecvMDB implements Mes
     public void onMessage(Message message) {
         TextMessage textMessage = (TextMessage) message;
         try {
-            System.out.println("Order Received \n"+ textMessage.getText());
+            System.out.println(&quot;Order Received \n&quot;+ textMessage.getText());
         } catch (JMSException e) {
             e.printStackTrace();
         }
@@ -183,14 +199,14 @@ public class OrderRecvMDB implements Mes
 }
 ]]></script>
 </div></div>
-<p>In this application there is a MDB that will listen on <b>OrderQueue</b>. <b>openejb-jar.xml</b> tells Geronimo that there is a MDB which is associated with the <b>jms-resources</b> JMS Resource Group. It links <b>OrderRecvMDB</b> with <b>OrderQueue</b> via <b>CommonConnectionFactory</b>.</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>openejb-jar.xml</b></div><div class="codeContent panelContent">
+<p>In this application there is a MDB that will listen on <strong>OrderQueue</strong>. <strong>openejb-jar.xml</strong> tells Geronimo that there is a MDB which is associated with the <strong>jms-resources</strong> JMS Resource Group. It links <strong>OrderRecvMDB</strong> with <strong>OrderQueue</strong> via <strong>CommonConnectionFactory</strong>.</p>
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>openejb-jar.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 &lt;openejb-jar
-    xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1"
-    xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1"
-    xmlns:security="http://geronimo.apache.org/xml/ns/security-1.1"
-    xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2"&gt;
+    xmlns=&quot;http://www.openejb.org/xml/ns/openejb-jar-2.1&quot;
+    xmlns:naming=&quot;http://geronimo.apache.org/xml/ns/naming-1.1&quot;
+    xmlns:security=&quot;http://geronimo.apache.org/xml/ns/security-1.1&quot;
+    xmlns:sys=&quot;http://geronimo.apache.org/xml/ns/deployment-1.2&quot;&gt;
     &lt;sys:environment&gt;
         &lt;sys:moduleId&gt;
 	    &lt;sys:groupId&gt;${pom.groupId}&lt;/sys:groupId&gt;
@@ -219,11 +235,11 @@ public class OrderRecvMDB implements Mes
 &lt;/openejb-jar&gt;
 ]]></script>
 </div></div>
-<p><b>geronimo-application.xml</b> and <b>application.xml</b> define the main components of the EAR. Both EJB component and Web archive information are given in these files as usual.&#160;&#160;This <b>geronimo-application.xml</b> also includes a section for defining&#160;a JMS queue and a common queue connection factory to access it. This is used for deploying the geronimo-activemq-ra.rar that is embedded in the ear.</p>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>geronimo-application.xml</b></div><div class="codeContent panelContent">
+<p><strong>geronimo-application.xml</strong> and <strong>application.xml</strong> define the main components of the EAR. Both EJB component and Web archive information are given in these files as usual.&#160;&#160;This <strong>geronimo-application.xml</strong> also includes a section for defining&#160;a JMS queue and a common queue connection factory to access it. This is used for deploying the geronimo-activemq-ra.rar that is embedded in the ear.</p>
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>geronimo-application.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;application xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-1.1"&gt;
-    &lt;environment xmlns="http://geronimo.apache.org/xml/ns/deployment-1.2"&gt;
+&lt;application xmlns=&quot;http://geronimo.apache.org/xml/ns/j2ee/application-1.1&quot;&gt;
+    &lt;environment xmlns=&quot;http://geronimo.apache.org/xml/ns/deployment-1.2&quot;&gt;
         &lt;moduleId&gt;
             &lt;groupId&gt;${pom.groupId}&lt;/groupId&gt;
             &lt;artifactId&gt;${pom.artifactId}&lt;/artifactId&gt;
@@ -233,8 +249,8 @@ public class OrderRecvMDB implements Mes
     &lt;/environment&gt;
     &lt;module&gt;
        &lt;connector&gt;geronimo-activemq-ra-2.0-SNAPSHOT.rar&lt;/connector&gt;
-        &lt;connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"&gt;
-            &lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"&gt;
+        &lt;connector xmlns=&quot;http://geronimo.apache.org/xml/ns/j2ee/connector-1.2&quot;&gt;
+            &lt;dep:environment xmlns:dep=&quot;http://geronimo.apache.org/xml/ns/deployment-1.2&quot;&gt;
                 &lt;dep:moduleId&gt;
                     &lt;dep:groupId&gt;${pom.groupId}&lt;/dep:groupId&gt;
                     &lt;dep:artifactId&gt;jms-resources&lt;/dep:artifactId&gt;
@@ -252,7 +268,7 @@ public class OrderRecvMDB implements Mes
             &lt;resourceadapter&gt;
                 &lt;resourceadapter-instance&gt;
                     &lt;resourceadapter-name&gt;jms-resources&lt;/resourceadapter-name&gt;
-                    &lt;nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2"&gt;
+                    &lt;nam:workmanager xmlns:nam=&quot;http://geronimo.apache.org/xml/ns/naming-1.2&quot;&gt;
                         &lt;nam:gbean-link&gt;DefaultWorkManager&lt;/nam:gbean-link&gt;
                     &lt;/nam:workmanager&gt;
                 &lt;/resourceadapter-instance&gt;
@@ -280,7 +296,7 @@ public class OrderRecvMDB implements Mes
                 &lt;adminobject-class&gt;org.apache.activemq.command.ActiveMQQueue&lt;/adminobject-class&gt;
                 &lt;adminobject-instance&gt;
                     &lt;message-destination-name&gt;OrderQueue&lt;/message-destination-name&gt;
-                    &lt;config-property-setting name="PhysicalName"&gt;OrderQueue&lt;/config-property-setting&gt;
+                    &lt;config-property-setting name=&quot;PhysicalName&quot;&gt;OrderQueue&lt;/config-property-setting&gt;
                 &lt;/adminobject-instance&gt;
             &lt;/adminobject&gt;
             &lt;adminobject&gt;
@@ -292,11 +308,11 @@ public class OrderRecvMDB implements Mes
 &lt;/application&gt;
 ]]></script>
 </div></div>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>application.xml</b></div><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>application.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
-             xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;application xmlns=&quot;http://java.sun.com/xml/ns/javaee&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; 
+             xsi:schemaLocation=&quot;http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd&quot; version=&quot;5&quot;&gt;
   &lt;description&gt;Geronimo Sample EAR for jms-mdb-sample&lt;/description&gt;
   &lt;display-name&gt;Geronimo Sample EAR for jms-mdb-sample&lt;/display-name&gt;
   &lt;module&gt;
@@ -315,18 +331,26 @@ public class OrderRecvMDB implements Mes
 ]]></script>
 </div></div>
 
-<h3><a shape="rect" name="JMSandMDBsampleapplication-ClientImplementation"></a>Client Implementation</h3>
+<h3 id="JMSandMDBsampleapplication-ClientImplementation">Client Implementation</h3>
+
+<p>The <strong>OrderSenderServlet.java</strong> servlet will parse the web form, create a message, and send that message to the OrderQueue via the CommonConnectoryFactory. </p>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
 
-<p>The <b>OrderSenderServlet.java</b> servlet will parse the web form, create a message, and send that message to the OrderQueue via the CommonConnectoryFactory. </p>
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Please note that Geronimo ignores the 'mappedName' configuration attribute for @Resource. Instead, use 'name' when annotating.</td></tr></table></div>
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>OrderSenderServlet.java</b></div><div class="codeContent panelContent">
+<p>Please note that Geronimo ignores the 'mappedName' configuration attribute for @Resource. Instead, use 'name' when annotating.</p>
+                    </div>
+    </div>
+
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>OrderSenderServlet.java</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
 public class OrderSenderServlet extends HttpServlet {
 
-    @Resource(name="CommonConnectionFactory")
+    @Resource(name=&quot;CommonConnectionFactory&quot;)
     private ConnectionFactory factory;
 
-    @Resource(name="OrderQueue")
+    @Resource(name=&quot;OrderQueue&quot;)
     private Queue receivingQueue;
 
     public void init() throws ServletException {
@@ -342,44 +366,44 @@ public class OrderSenderServlet extends 
     }
 
     private void manageOrders(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException{
-        String path = "/error.jsp";
+        String path = &quot;/error.jsp&quot;;
         Connection connection = null;
 	MessageProducer messageProducer = null;
 	Session sess = null;
 	try
         {
-	    String customerId = req.getParameter("customerId");
-	    String orderId = req.getParameter("orderId");
-	    String qty = req.getParameter("quantity");
-	    String model = req.getParameter("model");
+	    String customerId = req.getParameter(&quot;customerId&quot;);
+	    String orderId = req.getParameter(&quot;orderId&quot;);
+	    String qty = req.getParameter(&quot;quantity&quot;);
+	    String model = req.getParameter(&quot;model&quot;);
 
-	    if(!customerId.equals("") &amp;&amp; !orderId.equals("") &amp;&amp; !qty.equals("")){
-	    	System.out.println("Start Sending Order Request");
+	    if(!customerId.equals(&quot;&quot;) &amp;&amp; !orderId.equals(&quot;&quot;) &amp;&amp; !qty.equals(&quot;&quot;)){
+	    	System.out.println(&quot;Start Sending Order Request&quot;);
 	    	// creating online order request
-	    	String orderRequest = "&lt;Order orderId=\""+orderId+"\" custId=\""+customerId+"\" qty=\""+qty+"\" model=\""+model+"\"/&gt;" ;
+	    	String orderRequest = &quot;&lt;Order orderId=\&quot;&quot;+orderId+&quot;\&quot; custId=\&quot;&quot;+customerId+&quot;\&quot; qty=\&quot;&quot;+qty+&quot;\&quot; model=\&quot;&quot;+model+&quot;\&quot;/&gt;&quot; ;
 		connection = factory.createConnection();
 		sess = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
-		path = "/index.jsp";
-		TextMessage msg = sess.createTextMessage("&lt;OrderId=" + orderId + " CustomerId=" + customerId
-							+ " Quantity=" + qty + " Model=" + model + "&gt;" );
+		path = &quot;/index.jsp&quot;;
+		TextMessage msg = sess.createTextMessage(&quot;&lt;OrderId=&quot; + orderId + &quot; CustomerId=&quot; + customerId
+							+ &quot; Quantity=&quot; + qty + &quot; Model=&quot; + model + &quot;&gt;&quot; );
 		messageProducer = sess.createProducer(receivingQueue);
 		messageProducer.send(msg);
-		System.out.println("Order Request Send");
+		System.out.println(&quot;Order Request Send&quot;);
 	    } else{
-	    	String error = "";
+	    	String error = &quot;&quot;;
 
-	    	if(customerId.equals("")){
-	    	    error = "Customer Id Cannot be Empty";
-	    	}else if(orderId.equals("")){
-	    	    error = "Order Id Cannot be Empty";
-	    	}else if(qty.equals("")){
-	    	    error = "Quantity Cannot be Empty";
+	    	if(customerId.equals(&quot;&quot;)){
+	    	    error = &quot;Customer Id Cannot be Empty&quot;;
+	    	}else if(orderId.equals(&quot;&quot;)){
+	    	    error = &quot;Order Id Cannot be Empty&quot;;
+	    	}else if(qty.equals(&quot;&quot;)){
+	    	    error = &quot;Quantity Cannot be Empty&quot;;
 	    	}
-	    	req.setAttribute("error",error);
+	    	req.setAttribute(&quot;error&quot;,error);
 	    }
         } catch (Exception e)
         {
-            System.out.println("Error "+e);
+            System.out.println(&quot;Error &quot;+e);
             e.printStackTrace();
         } finally {
             try {
@@ -395,12 +419,12 @@ public class OrderSenderServlet extends 
 }
 ]]></script>
 </div></div>
-<p><b>web.xml</b> of the archive has the relevant configurations for the both queue connection factory and the queue, which is essential to refer to resources in a local enviroment.<br clear="none">
-</p><div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>web.xml</b></div><div class="codeContent panelContent">
+<p><strong>web.xml</strong> of the archive has the relevant configurations for the both queue connection factory and the queue, which is essential to refer to resources in a local enviroment.</p>
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;border-bottom-style: solid;"><b>web.xml</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-                       xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;web-app version=&quot;2.5&quot; xmlns=&quot;http://java.sun.com/xml/ns/javaee&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
+                       xsi:schemaLocation=&quot;http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd&quot;&gt;
     &lt;description&gt;JMS Servlet Sample&lt;/description&gt;
     &lt;servlet&gt;
         &lt;servlet-name&gt;OrderSenderServlet&lt;/servlet-name&gt;
@@ -432,60 +456,65 @@ public class OrderSenderServlet extends 
 
 &lt;/web-app&gt;
 ]]></script>
-</div></div>
-<div class="panelMacro"><table class="noteMacro"><colgroup span="1"><col span="1" width="24"><col span="1"></colgroup><tr><td colspan="1" rowspan="1" valign="top"><img align="middle" src="https://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" alt="" border="0"></td><td colspan="1" rowspan="1">Please note that this web application supports Servlet 2.5 specification. Some of the configurations in older versions (2.4) are slightly different than given in the above web.xml.</td></tr></table></div>
+</div></div>    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>Please note that this web application supports Servlet 2.5 specification. Some of the configurations in older versions (2.4) are slightly different than given in the above web.xml. </p>
+                    </div>
+    </div>
 
-<p><b>geronimo-web.xml</b> is not necessary in this case as the annotations will help resolve the queue or connection factory references.</p>
 
-<h2><a shape="rect" name="JMSandMDBsampleapplication-Toolsused"></a>Tools used</h2>
+<p><strong>geronimo-web.xml</strong> is not necessary in this case as the annotations will help resolve the queue or connection factory references.</p>
+
+<h2 id="JMSandMDBsampleapplication-Toolsused">Tools used</h2>
 
 <p>The tools used for developing and building the order placement application are:</p>
 
-<h3><a shape="rect" name="JMSandMDBsampleapplication-ApacheMaven2"></a>Apache Maven 2</h3>
+<h3 id="JMSandMDBsampleapplication-ApacheMaven2">Apache Maven 2</h3>
 
 <p>Maven is a popular open source build tool for enterprise Java projects, designed to take much of the hard work out of the build process. Maven uses a declarative approach, where the project structure and contents are described, rather than the task-based approach used in Ant or in traditional make files, for example. This helps enforce company-wide development standards and reduces the time needed to write and maintain build scripts. The declarative, lifecycle-based approach used by Maven 1 is, for many, a radical departure from more traditional build techniques, and Maven 2 goes even further in this regard. Maven 2 can be download from the following URL:<br clear="none">
 <a shape="rect" class="external-link" href="http://maven.apache.org">http://maven.apache.org</a></p>
 
-<h1><a shape="rect" name="JMSandMDBsampleapplication-Configuring%2CBuildingandDeployingtheSampleApplication"></a>Configuring, Building and Deploying the Sample Application <a shape="rect" name="JMSandMDBsampleapplication-configure"></a></h1>
+<h1 id="JMSandMDBsampleapplication-Configuring,BuildingandDeployingtheSampleApplicationconfigure">Configuring, Building and Deploying the Sample Application <span class="confluence-anchor-link" id="JMSandMDBsampleapplication-configure"></span></h1>
 
 <p>Download the order processing application from the following link:<br clear="none">
-<a shape="rect" href="jms-and-mdb-sample-application.data/jms-mdb-sample.zip?version=1&amp;modificationDate=1182852153000">jms-mdb-sample</a></p>
+<a shape="rect" href="jms-and-mdb-sample-application.data/jms-mdb-sample.zip?version=1&amp;modificationDate=1182852153000&amp;api=v2">jms-mdb-sample</a></p>
 
-<p>After decompressing the given file, the <b>jms-mdb-sample</b> directory will be created.</p>
+<p>After decompressing the given file, the <strong>jms-mdb-sample</strong> directory will be created.</p>
 
-<h2><a shape="rect" name="JMSandMDBsampleapplication-SourceCode"></a>Source Code</h2>
+<h2 id="JMSandMDBsampleapplication-SourceCode">Source Code</h2>
 
 <p>You can checkout the source code of this sample from SVN:</p>
 
 <p>svn checkout <a shape="rect" class="external-link" href="http://svn.apache.org/repos/asf/geronimo/samples/trunk/samples/jms-mdb-sample">http://svn.apache.org/repos/asf/geronimo/samples/trunk/samples/jms-mdb-sample</a></p>
 
-<h2><a shape="rect" name="JMSandMDBsampleapplication-Building"></a>Building</h2>
+<h2 id="JMSandMDBsampleapplication-Building">Building</h2>
 
-<p>The <b>jms-mdb-sample</b> folder will already contain an ear file ready to be deployed. However, you can still play with the source and build it yourself.</p>
+<p>The <strong>jms-mdb-sample</strong> folder will already contain an ear file ready to be deployed. However, you can still play with the source and build it yourself.</p>
 
-<p>Use a command prompt to navigate into the <b>jms-mdb-sample</b> directory and just give <b>mvn install site</b> command to build. It will overwrite the <b>jms-mdb-sample-ear-2.0-SNAPSHOT.ear</b> under the <b>jms-mdb-sample</b> folder.</p>
+<p>Use a command prompt to navigate into the <strong>jms-mdb-sample</strong> directory and just give <strong>mvn install site</strong> command to build. It will overwrite the <strong>jms-mdb-sample-ear-2.0-SNAPSHOT.ear</strong> under the <strong>jms-mdb-sample</strong> folder.</p>
 
-<h2><a shape="rect" name="JMSandMDBsampleapplication-Deploying"></a>Deploying</h2>
+<h2 id="JMSandMDBsampleapplication-Deploying">Deploying</h2>
 
 <p>Deploying Order processing sample application is pretty much the same as the deployment of JMS resources.</p>
-<ol><li>Navigate to <b>Deploy New</b> from the <b>Console Navigation</b> panel.</li><li>Load <b>jms-mdb-sample-ear-2.0-SNAPSHOT.ear</b> from <b>jms-mdb-sample</b> folder in to the <b>Archive</b> input box.</li><li>Press <b>Install</b> button to deploy application in the server.</li></ol>
+<ol><li>Navigate to <strong>Deploy New</strong> from the <strong>Console Navigation</strong> panel.</li><li>Load <strong>jms-mdb-sample-ear-2.0-SNAPSHOT.ear</strong> from <strong>jms-mdb-sample</strong> folder in to the <strong>Archive</strong> input box.</li><li>Press <strong>Install</strong> button to deploy application in the server.</li></ol>
 
 
-<h1><a shape="rect" name="JMSandMDBsampleapplication-TestingoftheSampleApplication"></a>Testing of the Sample Application <a shape="rect" name="JMSandMDBsampleapplication-testing"></a></h1>
+<h1 id="JMSandMDBsampleapplication-TestingoftheSampleApplicationtesting">Testing of the Sample Application <span class="confluence-anchor-link" id="JMSandMDBsampleapplication-testing"></span></h1>
 
 <p>To test the sample web application open a browser and type <a shape="rect" class="external-link" href="http://localhost:8080/order" rel="nofollow">http://localhost:8080/order</a>. It will forward you in to the Order Management Welcome page. Then user has to fill the necessary information for the order placement and submit it.</p>
 
-<p><span class="image-wrap" style="display: block; text-align: center"><img src="jms-and-mdb-sample-application.data/order_placement_web_app.gif" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image image-center" src="https://cwiki.apache.org/confluence/download/attachments/59620/order_placement_web_app.gif?version=1&amp;modificationDate=1181812981000&amp;api=v2" data-image-src="/confluence/download/attachments/59620/order_placement_web_app.gif?version=1&amp;modificationDate=1181812981000&amp;api=v2"></p>
 
 <p>After processing an order you will see the message printed to your console.</p>
 
-<h1><a shape="rect" name="JMSandMDBsampleapplication-Summary"></a>Summary <a shape="rect" name="JMSandMDBsampleapplication-summary"></a></h1>
+<h1 id="JMSandMDBsampleapplication-Summarysummary">Summary <span class="confluence-anchor-link" id="JMSandMDBsampleapplication-summary"></span></h1>
 
 <p>This article has demonstrated the use of JMS features in Apache Geronimo with the ActiveMQ JMS server. It provides a hypothetical example which extensively used JMS features.</p>
 
 <p>Some of the highlights of this article : -</p>
-<ul><li>Define JMS connection factories and related queues in a Geronimo enviroment.</li><li>Message Driven Beans are the components listening on JMS queues providing by the J2EE container.</li></ul>
-</div>
+<ul><li>Define JMS connection factories and related queues in a Geronimo enviroment.</li><li>Message Driven Beans are the components listening on JMS queues providing by the J2EE container.</li></ul></div>
         </div>
 
         

Modified: websites/production/geronimo/content/GMOxDOC20/jms-resources-deployment-with-deploy-tool.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/jms-resources-deployment-with-deploy-tool.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/jms-resources-deployment-with-deploy-tool.html Tue Jul 29 00:52:18 2014
@@ -21,7 +21,6 @@
   <link href='http://geronimo.apache.org/resources/highlighter/styles/shCoreGeronimo.css' rel='stylesheet' type='text/css' />
   <link href='http://geronimo.apache.org/resources/highlighter/styles/shThemeGeronimo.css' rel='stylesheet' type='text/css' />
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shCore.js' type='text/javascript'></script>
-  <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushJava.js' type='text/javascript'></script>
   <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushXml.js' type='text/javascript'></script>
   
   <script type="text/javascript">
@@ -97,10 +96,10 @@
         <div class="wiki-content">
           <div class="wiki-content maincontent"><p>You can deploy jms resources with deploy command (without web console). When you want to create a group of resources consist of ConnectionFactory, topics and queues you only have to deploy a geronimo-activemq-ra connector (RA meaning "ResourceAdapter") with an deploy plan like this...</p>
 
-<div class="code panel" style="border-style: solid;border-width: 1px;"><div class="codeContent panelContent">
+<div class="code panel pdl" style="border-style: solid;border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-&lt;connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"&gt;
-  &lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"&gt;
+&lt;connector xmlns=&quot;http://geronimo.apache.org/xml/ns/j2ee/connector-1.2&quot;&gt;
+  &lt;dep:environment xmlns:dep=&quot;http://geronimo.apache.org/xml/ns/deployment-1.2&quot;&gt;
     &lt;dep:moduleId&gt;
     	&lt;dep:groupId&gt;console.jms&lt;/dep:groupId&gt;
     	&lt;dep:artifactId&gt;jmsResources&lt;/dep:artifactId&gt;
@@ -118,7 +117,7 @@
   &lt;resourceadapter&gt;
     &lt;resourceadapter-instance&gt;
       &lt;resourceadapter-name&gt;jmsResources&lt;/resourceadapter-name&gt;
-      &lt;workmanager xmlns="http://geronimo.apache.org/xml/ns/naming-1.2"&gt;
+      &lt;workmanager xmlns=&quot;http://geronimo.apache.org/xml/ns/naming-1.2&quot;&gt;
         &lt;gbean-link&gt;DefaultWorkManager&lt;/gbean-link&gt;
       &lt;/workmanager&gt;
     &lt;/resourceadapter-instance&gt;
@@ -152,7 +151,7 @@
     &lt;adminobject-class&gt;org.apache.activemq.command.ActiveMQTopic&lt;/adminobject-class&gt;
     &lt;adminobject-instance&gt;
       &lt;message-destination-name&gt;ElementSupportData&lt;/message-destination-name&gt;
-      &lt;config-property-setting name="PhysicalName"&gt;ElementSupportData&lt;/config-property-setting&gt;
+      &lt;config-property-setting name=&quot;PhysicalName&quot;&gt;ElementSupportData&lt;/config-property-setting&gt;
     &lt;/adminobject-instance&gt;
   &lt;/adminobject&gt;
    
@@ -163,7 +162,7 @@
     &lt;adminobject-class&gt;org.apache.activemq.command.ActiveMQQueue&lt;/adminobject-class&gt;
     &lt;adminobject-instance&gt;
       &lt;message-destination-name&gt;SampleQueue&lt;/message-destination-name&gt;
-      &lt;config-property-setting name="PhysicalName"&gt;SampleQueue&lt;/config-property-setting&gt;
+      &lt;config-property-setting name=&quot;PhysicalName&quot;&gt;SampleQueue&lt;/config-property-setting&gt;
     &lt;/adminobject-instance&gt;
   &lt;/adminobject&gt;
   
@@ -173,13 +172,13 @@
 
 <p>Now you only have to deploy it with this command (I named deploy plan as JmsResources.xml) ussing for this example geronimo 2.0.2:</p>
 
-<p><b><tt>java -jar %GERONIMO_HOME%/bin/deployer.jar --user system --password manager --host localhost deploy JmsResources.xml %GERONIMO_HOME%/repository/org/apache/geronimo/modules/geronimo-activemq-ra/2.0.2/geronimo-activemq-ra-2.0.2.rar</tt></b></p>
+<p><strong><code>java -jar %GERONIMO_HOME%/bin/deployer.jar --user system --password manager --host localhost deploy JmsResources.xml %GERONIMO_HOME%/repository/org/apache/geronimo/modules/geronimo-activemq-ra/2.0.2/geronimo-activemq-ra-2.0.2.rar</code></strong></p>
 
 <p>Remember that geronimo-activemq-ra-2.0.2.rar path or name can change according to the geronimo 2.x installation that you have. If deploy works well, in Geronimo Web Console-&gt; JMS Resources will appear a new JMS Resource group named jmsResources (console.jms/jmsResources/1.0/rar). console.jms/jmsResources/1.0/rar  is the component name created ussing data defined in moduleId tag.</p>
 
 <p>If you want to undeploy it, you can do it from  Geronimo Web Console -&gt; J2EE connectors or with deploy command as this manner...</p>
 
-<p><b><tt>java -jar %GERONIMO_HOME%/bin/deployer.jar --user system --password manager --host localhost undeploy console.jms/jmsResources/1.0/rar</tt></b></p>
+<p><strong><code>java -jar %GERONIMO_HOME%/bin/deployer.jar --user system --password manager --host localhost undeploy console.jms/jmsResources/1.0/rar</code></strong></p>
 
 <p>Remember set RemoteDeployHostname into %GERONIMO_HOME%\var\config\config-substitutions.properties if you want to do remote deploy (when --host parameter is not the localhost).</p></div>
         </div>



Mime
View raw message