geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r917744 [16/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-ejb-bmp-migration.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-ejb-bmp-migration.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-ejb-bmp-migration.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,43 +96,56 @@
 
       <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="j2g-migration-tool.html" rel="prev">
+                                    <span class="aui-icon aui-icon-small atb-icon-arrow-left">Previous</span>
+                                <span class="title">J2G Migration Tool</span>
+            </a>
 
-/*]]>*/</style><div class="Scrollbar"><table class="ScrollbarTable"><tr><td colspan="1" rowspan="1" class="ScrollbarPrevIcon"><a shape="rect" href="j2g-migration-tool.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="j2g-migration-tool.html">J2G Migration Tool</a>&#160;</td><td colspan="1" rowspan="1" class="ScrollbarParent" width="33%"><sup><a shape="rect" href="migrating-to-apache-geronimo.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="migrating-to-apache-geronimo.html">Migrating to Apache Geronimo</a></td><td colspan="1" rowspan="1" class="ScrollbarNextName" width="33%">&#160;<a shape="rect" href="jboss-to-geronimo-ejb-cmp-migration.html">JBoss to Geronimo - EJB-CMP Migration</a></td><td colspan="1" row
 span="1" class="ScrollbarNextIcon"><a shape="rect" href="jboss-to-geronimo-ejb-cmp-migration.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="JBosstoGeronimo-EJB-BMPMigration-top"></a><br clear="none">
+    </div>
+    <div class="parent">
+                    <a shape="rect" href="migrating-to-apache-geronimo.html" rel="parent">
+                                            <span class="aui-icon aui-icon-small atb-icon-arrow-up">Up</span>
+                                        <span class="title">Migrating to Apache Geronimo</span>
+                </a>
+
+            </div>
+    <div class="next">
+        <a shape="rect" href="jboss-to-geronimo-ejb-cmp-migration.html" rel="next">
+                <span class="title">JBoss to Geronimo - EJB-CMP Migration</span>
+                                    <span class="aui-icon aui-icon-small atb-icon-arrow-right">Next</span>
+                            </a>
+
+    </div>
+</div>
+<p><span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-BMPMigration-top"></span><br clear="none">
 An entity bean is defined as a representation of persistent data that has the ability to read from database and populate its fields with data. It can be updated and stored back to the database. There are two types of Entity Beans that come with Enterprise Java Beans: Bean-Managed Persistence(BMP) and Container-Managed Persistent(CMP). This article covers the migration of a BMP sample application. For this type of entity bean, actual code must be written to handle persistent operations such as loading, saving and finding data. The developer must use persistence API such as JDBC to select, insert, update, delete from a database.</p>
 
 <p>This article is organized in the following sections:</p>
 <ul><li><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-analysis">BMP implementation analysis</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-sample">Sample application</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-jboss">The JBoss environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-geronimo">The Geronimo environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-migration">Step-by-step migration</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-summary">Summary</a></li></ul>
 
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-BMPimplementationanalysis"></a>BMP implementation analysis <a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-analysis"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-BMPMigration-BMPimplementationanalysisanalysis">BMP implementation analysis <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-BMPMigration-analysis"></span></h1>
 
 <p>BMP implementation may vary from one vendor to another. The purpose of this section is to provide a BMP specific feature-to-feature comparison between JBoss v4.0.5 and Apache Geronimo, so that you can clearly identify the differences and plan accordingly before migration.</p>
 
-<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Features</th><th colspan="1" rowspan="1" class="confluenceTh">JBoss v4.2.1</th><th colspan="1" rowspan="1" class="confluenceTh">Apache Geronimo</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">EJB Container</td><td colspan="1" rowspan="1" class="confluenceTd">JBoss comes with its own implementation</td><td colspan="1" rowspan="1" class="confluenceTd">Geronimo uses OpenEJB as its EJB Container</td></tr></tbody></table>
-</div>
+<div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Features</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>JBoss v4.2.1</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Apache Geronimo</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>EJB Container</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>JBoss comes with its own implementation</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Geronimo uses OpenEJB as its EJB Container</p></td></tr></tbody></table></div>
 
 
 <p><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Sampleapplication"></a>Sample application <a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-sample"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-BMPMigration-Sampleapplicationsample">Sample application <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-BMPMigration-sample"></span></h1>
 
 <p>This is a simple loan registration application which allows users to apply for loans and administrators to approve/reject the loans. Customers can apply for loans using the Web site while the manager uses a simple Java application to approval/reject loans. BMP Entity Bean has been used to manage Loan related persistence data from a database. In addition to that a Stateless Session Bean has been used handle work flow related activities. </p>
 
 <p>The following figure illustrates the loan management Web application flow:<br clear="none">
-<span class="image-wrap" style="display: block; text-align: center"><img src="jboss-to-geronimo-ejb-bmp-migration.data/loan_web_overview.gif" style="border: 0px solid black"></span></p>
+<img class="confluence-embedded-image image-center" src="https://cwiki.apache.org/confluence/download/attachments/65034/loan_web_overview.gif?version=1&amp;modificationDate=1189417192000&amp;api=v2" data-image-src="/confluence/download/attachments/65034/loan_web_overview.gif?version=1&amp;modificationDate=1189417192000&amp;api=v2"></p>
 
 <p>First page of the loan registration Web application acts as a notice board which displays list of loans and their current status. When a customer decides to apply for a Loan, he/she can use loan registration form. After the registration of the loan, it is categorized under pending status. A manager who has the administrator privileges will use a small application to change the status of loans. Using this application, the manager can change the status of pending loans to either approved or rejected. </p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-ApplicationclassesandJSPpages"></a>Application classes and JSP pages</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-ApplicationclassesandJSPpages">Application classes and JSP pages</h2>
 
 <ul><li>org.apache.geronimo.samples.loan.client
 	<ul><li>LoanStatusChanger - Standalone application which helps to approve applied loans.</li></ul>
@@ -150,20 +164,20 @@ An entity bean is defined as a represent
 <ul><li>error.jsp -  Common error page to handle unexpected conditions.</li><li>index.jsp - Forward in to the list of loans in the application.</li><li>list_loans.jsp - List of loans and their information are displayed.</li><li>register_loan.jsp - Loan registration form to be filled by a customer.</li></ul>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Toolsused"></a>Tools used</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Toolsused">Tools used</h2>
 <p>The tools used for developing and building the Loan Manager application are:</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Eclipse"></a>Eclipse</h3>
+<h3 id="JBosstoGeronimo-EJB-BMPMigration-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-EJB-BMPMigration-ApacheAnt"></a>Apache Ant</h3>
+<h3 id="JBosstoGeronimo-EJB-BMPMigration-ApacheAnt">Apache Ant</h3>
 <p>Ant is a pure Java build tool. It is used for building the war files and populating the database for the Online Brokerage 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-EJB-BMPMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-TheJBossenvironment"></a>The JBoss environment <a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-jboss"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-BMPMigration-TheJBossenvironmentjboss">The JBoss environment <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-BMPMigration-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. Note that for this migration example JBoss v4.2.1 was used.</p>
 
@@ -171,45 +185,51 @@ An entity bean is defined as a represent
 
 <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.2.1 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.2.1 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 <b>run.sh -c &lt;your_server_name&gt;</b> 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 step is described in the following section.</li></ol>
+<ol><li>Download and install JBoss v4.2.1 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.2.1 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 <strong>run.sh -c &lt;your_server_name&gt;</strong> 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 prerequi
 site software required by the sample application. This step is described in the following section.</li></ol>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Installandconfigureprerequisitesoftware"></a>Install and configure prerequisite software</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Installandconfigureprerequisitesoftware">Install and configure prerequisite software</h2>
 <p>In order to build and run the Loan Management application included in this article, you will need to install and configure the build tool and the database that is used by the application.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Modifydatabasesettings"></a>Modify database settings</h3>
+<h3 id="JBosstoGeronimo-EJB-BMPMigration-Modifydatabasesettings">Modify database settings</h3>
+
+<p>This application is using the HSQL database that comes as part of the JBoss bundle. You need to modify the script for creating the database. Edit the <strong>localDB.script</strong> file located in the <strong>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\data\hypersonic</strong> directory:</p>
 
-<p>This application is using the HSQL database that comes as part of the JBoss bundle. You need to modify the script for creating the database. Edit the <b>localDB.script</b> file located in the <b>&lt;jboss_home&gt;\server\&lt;your_server_name&gt;\data\hypersonic</b> directory:</p>
+<p>Add the top of the <strong>localDB.script</strong> file the content of the following example in order to create the sample HSQL database. Also add the sample data to the same file at the end given in the <strong>config/db.sql</strong> under the JBoss Specific Data.</p>
 
-<p>Add the top of the <b>localDB.script</b> file the content of the following example in order to create the sample HSQL database. Also add the sample data to the same file at the end given in the <b>config/db.sql</b> under the JBoss Specific Data.</p>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p><strong>Make sure JBoss is not running at the time of modifying this file.</strong></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"><b>Make sure JBoss is not running at the time of modifying this file.</b></td></tr></table></div>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-ConfigureAnt"></a>Configure Ant</h3>
+<h3 id="JBosstoGeronimo-EJB-BMPMigration-ConfigureAnt">Configure Ant</h3>
 
-<p>As mentioned before, Apache Ant is used to build the binaries for the Online Brokerage 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 Online Brokerage 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>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-ConfigureXDoclet"></a>Configure XDoclet</h3>
+<h3 id="JBosstoGeronimo-EJB-BMPMigration-ConfigureXDoclet">Configure XDoclet</h3>
 
 <p>XDoclet is going to be used as build tool for the configuration file generation. It  is an open source code generation engine. It enables Attribute-Oriented Programming for Java. In short, this means that you can add more significance to your code by adding meta data (attributes) to your Java sources. This is done in special JavaDoc tags.<br clear="none">
 Although XDoclet originated as a tool for creating EJBs, it has evolved into a general-purpose code generation engine. XDoclet consists of a core and a constantly growing number of modules. It is fairly straight forward to write new modules if there is a need for a new kind of component.<br clear="none">
 <a shape="rect" class="external-link" href="http://xdoclet.sourceforge.net/xdoclet/index.html" rel="nofollow">http://xdoclet.sourceforge.net/xdoclet/index.html</a></p>
 
-<p>Just extract the latest version of the XDoclet and set the <b>xdoclet.home</b> parameter in to the <b>build.properties</b> file.</p>
+<p>Just extract the latest version of the XDoclet and set the <strong>xdoclet.home</strong> parameter in to the <strong>build.properties</strong> file.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Buildthesampleapplication"></a>Build the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Buildthesampleapplication">Build the sample application</h2>
 
 <p>The loan manager application included with this article provides an Ant script that you will use in order to build the application. Download the loan manager application from the following link:</p>
 
-<p><a shape="rect" href="jboss-to-geronimo-ejb-bmp-migration.data/loan.zip?version=1&amp;modificationDate=1189417201000">Loan</a></p>
+<p><a shape="rect" href="jboss-to-geronimo-ejb-bmp-migration.data/loan.zip?version=1&amp;modificationDate=1189417201000&amp;api=v2">Loan</a></p>
 
-<p>After extracting the zip file, a <b>loan</b> directory is created. In that directory open the build.properties file and edit the properties to match your environment as shown in the following example:</p>
+<p>After extracting the zip file, a <strong>loan</strong> directory is created. In that directory open the build.properties file and edit the properties to match your environment as 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>build.properties</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.properties</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 ## Set the Geronimo 2.0 home here
 geronimo.home=&lt;geronimo_home&gt;
@@ -219,61 +239,75 @@ xdoclet.home=&lt;xdoclet_home&gt;
 ]]></script>
 </div></div>
 
-<p>Before starting the build process just set the correct paths for the <b>geronimo.home</b> and <b>xdoclet.home</b> entries in the <b>build.properties</b> file in the <b>config</b> directory.</p>
+<p>Before starting the build process just set the correct paths for the <strong>geronimo.home</strong> and <strong>xdoclet.home</strong> entries in the <strong>build.properties</strong> file in the <strong>config</strong> directory.</p>
 
-<p>From a command prompt or shell go to the <b>loan</b> directory and run <b>ant jboss</b>. This will build the ear file and place it directly in the <b>releases/jboss</b> directory.</p>
+<p>From a command prompt or shell go to the <strong>loan</strong> directory and run <strong>ant jboss</strong>. This will build the ear file and place it directly in the <strong>releases/jboss</strong> directory.</p>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Deploythesampleapplication"></a>Deploy the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Deploythesampleapplication">Deploy the sample application</h2>
 
-<p>To deploy the sample application just copy the <b>Loan.ear</b> will be created under the <b>loan/releases/jboss</b> folder to the <b>&lt;jboss_home&gt;/server/&lt;your_server_name&gt;/deploy</b> folder. </p>
+<p>To deploy the sample application just copy the <strong>Loan.ear</strong> will be created under the <strong>loan/releases/jboss</strong> folder to the <strong>&lt;jboss_home&gt;/server/&lt;your_server_name&gt;/deploy</strong> folder. </p>
 
 <p>If JBoss is already started, it will automatically deploy and start the application; otherwise, the application will be deployed and started at the next startup.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Testthesampleapplication"></a>Test the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Testthesampleapplication">Test the sample application</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/loan" rel="nofollow">http://localhost:8080/loan</a></p>
 
-<p>This brings up the loan manager main page with the list of loans and their current statuses.<b>Register</b> link will forward you to the loan registration form which accepts number of fields before adding loans in to the loan information database. </p>
+<p>This brings up the loan manager main page with the list of loans and their current statuses.<strong>Register</strong> link will forward you to the loan registration form which accepts number of fields before adding loans in to the loan information database. </p>
 
-<p><span class="image-wrap" style="display: block; text-align: center"><img src="jboss-to-geronimo-ejb-bmp-migration.data/loan_screen.gif" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image image-center" src="https://cwiki.apache.org/confluence/download/attachments/65034/loan_screen.gif?version=1&amp;modificationDate=1189417184000&amp;api=v2" data-image-src="/confluence/download/attachments/65034/loan_screen.gif?version=1&amp;modificationDate=1189417184000&amp;api=v2"></p>
 
 <p>To change the status of a loan, manager has to find the loan ID from the Web application and has to provide it in the client application as given below.</p>
 
-<p><b>java -jar LoanStatusChanger.jar &lt;loanId&gt; &lt;status&gt;</b></p>
+<p><strong>java -jar LoanStatusChanger.jar &lt;loanId&gt; &lt;status&gt;</strong></p>
 
 <p>Status filed will change according to the following values. The following are the status values of relevant loans.</p>
 <ol><li>0 - Pending</li><li>1 - Accepted</li><li>Other - Rejected</li></ol>
 
 
-<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">Make sure you add the <b>&lt;jboss-home&gt;/client/jbossall-client.jar</b> file to your class path before running the above command.</td></tr></table></div>
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            <p>Make sure you add the <strong>&lt;jboss-home&gt;/client/jbossall-client.jar</strong> file to your class path before running the above command.</p>
+                    </div>
+    </div>
+
 
 <p><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-TheGeronimoenvironment"></a>The Geronimo environment <a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-geronimo"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-BMPMigration-TheGeronimoenvironmentgeronimo">The Geronimo environment <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-BMPMigration-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-EJB-BMPMigration-top">Back to Top</a></p>
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Stepbystepmigration"></a>Step-by-step migration <a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-migration"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-BMPMigration-Step-by-stepmigrationmigration">Step-by-step migration <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-BMPMigration-migration"></span></h1>
 
-<p>When you built the loan manager sample application, Ant packaged the deployment descriptors for both JBoss <b>jboss.xml</b> and Geronimo <b>openejb-jar.xml</b> as they were already provided by the sample application. These files are located in the <b>loan/config</b> directory.</p>
+<p>When you built the loan manager sample application, Ant packaged the deployment descriptors for both JBoss <strong>jboss.xml</strong> and Geronimo <strong>openejb-jar.xml</strong> as they were already provided by the sample application. These files are located in the <strong>loan/config</strong> directory.</p>
 
 <p>The following example shows the JBoss deployment descriptor.</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.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.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;!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;!DOCTYPE jboss PUBLIC &quot;-//JBoss//DTD JBOSS 4.0//EN&quot; &quot;http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd&quot;&gt;
 
 &lt;jboss&gt;
 
@@ -305,11 +339,11 @@ xdoclet.home=&lt;xdoclet_home&gt;
 
 <p>Compare it with the contents of the Geronimo deployment plan 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>openejb-jar.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>openejb-jar.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;openejb-jar xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1"&gt;
-	&lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;openejb-jar xmlns=&quot;http://www.openejb.org/xml/ns/openejb-jar-2.1&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;org.apache.geronimo.samples&lt;/dep:groupId&gt;
 			&lt;dep:artifactId&gt;LoanManagerEJB&lt;/dep:artifactId&gt;
@@ -340,13 +374,13 @@ xdoclet.home=&lt;xdoclet_home&gt;
 ]]></script>
 </div></div>
 
-<p>First difference can be clearly noted is Geronimo specific configuration has additional information than JBoss specific one. That part of the Geronimo configuration file is quite similar to a Maven 2 build script. Both of these given configuration files have EJB information. JBoss uses local JNDI names to link the EJBs while Geronimo directly use the EJB's name. In addition to above differences the <b>openejb-jar.xml</b> file clearly gives the EJB reference information than the <b>jboss.xml</b> file.</p>
+<p>First difference can be clearly noted is Geronimo specific configuration has additional information than JBoss specific one. That part of the Geronimo configuration file is quite similar to a Maven 2 build script. Both of these given configuration files have EJB information. JBoss uses local JNDI names to link the EJBs while Geronimo directly use the EJB's name. In addition to above differences the <strong>openejb-jar.xml</strong> file clearly gives the EJB reference information than the <strong>jboss.xml</strong> file.</p>
 
 <p>The Web archive related configuration files give you few more differences.</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-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>jboss-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;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 
 
 &lt;jboss-web&gt;
@@ -359,11 +393,11 @@ xdoclet.home=&lt;xdoclet_home&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>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-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 xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1" xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1"&gt;
-  &lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&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;&gt;
+  &lt;dep:environment xmlns:dep=&quot;http://geronimo.apache.org/xml/ns/deployment-1.1&quot;&gt;
     &lt;dep:moduleId&gt;
       &lt;dep:groupId&gt;org.apache.geronimo.samples&lt;/dep:groupId&gt;
       &lt;dep:artifactId&gt;LoanManagerWeb&lt;/dep:artifactId&gt;
@@ -384,30 +418,30 @@ xdoclet.home=&lt;xdoclet_home&gt;
 ]]></script>
 </div></div>
 
-<p><b>jboss-web.xml</b> maps the EJBs using JNDI names as given above while <b>geronimo-web.xml</b> directly uses the EJB's name. The reference names given in each mapping will be used refer EJBs from the Servlets. <b>web.xml</b> file of the WAR file contains more information about each EJB reference name, which will be common to the both Geronimo and JBoss flavors of this application.</p>
+<p><strong>jboss-web.xml</strong> maps the EJBs using JNDI names as given above while <strong>geronimo-web.xml</strong> directly uses the EJB's name. The reference names given in each mapping will be used refer EJBs from the Servlets. <strong>web.xml</strong> file of the WAR file contains more information about each EJB reference name, which will be common to the both Geronimo and JBoss flavors of this application.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Buildthesampleapplication"></a>Build the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Buildthesampleapplication.1">Build the sample application</h2>
 
-<p>Build the migrated Geronimo version of the sample application by running following command from the <b>loan</b> directory.<br clear="none">
-<b>ant geronimo</b><br clear="none">
-It will create <b>Loan.ear</b> file in the <b>loan/releases/geronimo</b> folder.</p>
+<p>Build the migrated Geronimo version of the sample application by running following command from the <strong>loan</strong> directory.<br clear="none">
+<strong>ant geronimo</strong><br clear="none">
+It will create <strong>Loan.ear</strong> file in the <strong>loan/releases/geronimo</strong> folder.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Deploythemigratedapplication"></a>Deploy the migrated application</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Deploythemigratedapplication">Deploy the migrated application</h2>
 
 <p>To deploy the migrated Loan Manager application, make sure the Geronimo server is up and running and user has to populate the database and then deploy the sample application.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-PopulatingtheDatabase"></a>Populating the Database</h3>
+<h3 id="JBosstoGeronimo-EJB-BMPMigration-PopulatingtheDatabase">Populating the Database</h3>
 <p>This sample application will use the default Geronimo System database to hold the application specific data.<br clear="none">
 In the Geronimo console follow given steps.</p>
-<ol><li>Select DB Manager link from the Console Navigation in the left.</li><li>Select the <b>SystemDatabase</b> to <b>Use DB</b> field.</li><li>Open <b>db.sql</b> in the <b>loan/config</b> directory from a text editor and copy the content below Geronimo Specific Database SQLs.</li><li>Paste the content the given above SQL Commands text area and press Run SQL button.</li></ol>
+<ol><li>Select DB Manager link from the Console Navigation in the left.</li><li>Select the <strong>SystemDatabase</strong> to <strong>Use DB</strong> field.</li><li>Open <strong>db.sql</strong> in the <strong>loan/config</strong> directory from a text editor and copy the content below Geronimo Specific Database SQLs.</li><li>Paste the content the given above SQL Commands text area and press Run SQL button.</li></ol>
 
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-DeploySampleApplication"></a>Deploy Sample Application</h3>
+<h3 id="JBosstoGeronimo-EJB-BMPMigration-DeploySampleApplication">Deploy Sample Application</h3>
 <p>Open Geronimo console in your browser and follow the given steps:</p>
-<ol><li>Scroll down to <b>Deploy New</b> from the <b>Console Navigation</b> panel.</li><li>Load <b>loan.ear</b> from <b>loan/releases/geronimo</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>Scroll down to <strong>Deploy New</strong> from the <strong>Console Navigation</strong> panel.</li><li>Load <strong>loan.ear</strong> from <strong>loan/releases/geronimo</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>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Testthesampleapplication"></a>Test the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-BMPMigration-Testthesampleapplication.1">Test the sample application</h2>
 
 <p>To test the application, open a Web browser and access the following URL:</p>
 
@@ -415,21 +449,27 @@ In the Geronimo console follow given ste
 
 <p>To change the status of a loan, the user has to find the loan ID from the Web application and has to provide it in the client application as given below.</p>
 
-<p><b>java -jar LoanStatusChanger.jar &lt;loanId&gt; &lt;status&gt;</b></p>
+<p><strong>java -jar LoanStatusChanger.jar &lt;loanId&gt; &lt;status&gt;</strong></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">Make sure you add the following list of JAR files to your class path before running the above command.
+    <div class="aui-message warning shadowed information-macro">
+                            <span class="aui-icon icon-warning">Icon</span>
+                <div class="message-content">
+                            
+<p>Make sure you add the following list of JAR files to your class path before running the above command.</p>
 <ol><li>geronimo-kernel-2.0.x.jar</li><li>geronimo-j2ee_connector_1.5_spec-1.x.x.jar</li><li>geronimo-j2ee_management_1.1_spec-1.x.jar</li><li>geronimo-security-2.0.x.jar</li><li>cglib-nodep-2.1_3.jar</li><li>openejb-core-3.0.jar</li></ol>
-</td></tr></table></div>
+
+                    </div>
+    </div>
+
 
 <p><a shape="rect" href="#JBosstoGeronimo-EJB-BMPMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-Summary"></a>Summary <a shape="rect" name="JBosstoGeronimo-EJB-BMPMigration-summary"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-BMPMigration-Summarysummary">Summary <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-BMPMigration-summary"></span></h1>
 <p>This article has shown how to migrate a sample application that uses BMP entity beans, from JBoss v4.2.1 to Apache Geronimo. This article provided step-by-step instructions to build the application, deploy and run it, and then migrate it to the Geronimo environment.</p>
 
 <p>The following list summarizes the major differences found during this sample application migration.</p>
 
-<ul><li>In order to deploy an EJB jar file in JBoss you need to just copy the configuration file to the deploy directory but in Geronimo you can use either deployer tool, console or hot deployment directory.</li><li>The contents of the deployment plans for EJB jar files in JBoss and in Geronimo are almost similar except for the starting part of the Geronimo which is more similar to a Maven 2 build file.</li></ul>
-</div>
+<ul><li>In order to deploy an EJB jar file in JBoss you need to just copy the configuration file to the deploy directory but in Geronimo you can use either deployer tool, console or hot deployment directory.</li><li>The contents of the deployment plans for EJB jar files in JBoss and in Geronimo are almost similar except for the starting part of the Geronimo which is more similar to a Maven 2 build file.</li></ul></div>
         </div>
 
         

Modified: websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-ejb-session-beans-migration.html
==============================================================================
--- websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-ejb-session-beans-migration.html (original)
+++ websites/production/geronimo/content/GMOxDOC20/jboss-to-geronimo-ejb-session-beans-migration.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="jboss-to-geronimo-ejb-mdb-migration.html" rel="prev">
+                                    <span class="aui-icon aui-icon-small atb-icon-arrow-left">Previous</span>
+                                <span class="title">JBoss to Geronimo - EJB-MDB Migration</span>
+            </a>
 
-/*]]>*/</style><div class="Scrollbar"><table class="ScrollbarTable"><tr><td colspan="1" rowspan="1" class="ScrollbarPrevIcon"><a shape="rect" href="jboss-to-geronimo-ejb-mdb-migration.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="jboss-to-geronimo-ejb-mdb-migration.html">JBoss to Geronimo - EJB-MDB Migration</a>&#160;</td><td colspan="1" rowspan="1" class="ScrollbarParent" width="33%"><sup><a shape="rect" href="migrating-to-apache-geronimo.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="migrating-to-apache-geronimo.html">Migrating to Apache Geronimo</a></td><td colspan="1" rowspan="1" class="ScrollbarNextName" width="33%">&#160;<a shape="rect" href="jboss-to-geronimo-hibernate-migration.html">JBoss to G
 eronimo - Hibernate Migration</a></td><td colspan="1" rowspan="1" class="ScrollbarNextIcon"><a shape="rect" href="jboss-to-geronimo-hibernate-migration.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="JBosstoGeronimo-EJB-SessionBeansMigration-top"></a><br clear="none">
+    </div>
+    <div class="parent">
+                    <a shape="rect" href="migrating-to-apache-geronimo.html" rel="parent">
+                                            <span class="aui-icon aui-icon-small atb-icon-arrow-up">Up</span>
+                                        <span class="title">Migrating to Apache Geronimo</span>
+                </a>
+
+            </div>
+    <div class="next">
+        <a shape="rect" href="jboss-to-geronimo-hibernate-migration.html" rel="next">
+                <span class="title">JBoss to Geronimo - Hibernate Migration</span>
+                                    <span class="aui-icon aui-icon-small atb-icon-arrow-right">Next</span>
+                            </a>
+
+    </div>
+</div>
+<p><span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-SessionBeansMigration-top"></span><br clear="none">
 A typical J2EE application may contain Enterprise JavaBeans or EJBs. These beans contain the application's business logic and live business data. Although it is possible to use standard Java objects to contain your business logic and business data, using EJBs addresses many of the issues of using simple Java objects, such as scalability, lifecycle management and state management.</p>
 
 <p>This document discusses one type of EJBs, the Session EJB. This type of EJBs are useful for mapping business process flow (or equivalent application concepts). There are two types of Session EJBs, stateless and stateful. This article addresses both these Session Bean types and shows how to use them in a practical scenario.</p>
@@ -115,27 +131,25 @@ A typical J2EE application may contain E
 <ul><li><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-analysis">EJB implementation analysis</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-sample">Sample application</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-jboss">The JBoss environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-geronimo">The Geronimo environment</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-migration">Step-by-step migration</a></li><li><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-summary">Summary</a></li></ul>
 
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-EJBimplementationanalysis"></a>EJB implementation analysis <a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-%23analysis"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-SessionBeansMigration-EJBimplementationanalysis#analysis">EJB implementation analysis <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-SessionBeansMigration-#analysis"></span></h1>
 
 <p>EJB implementation may vary from one vendor to another. The purpose of this section is to provide a session bean specific feature-to-feature comparison between JBoss and Apache Geronimo so you can clearly identify the differences and plan accordingly before migration.</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.0.5</th><th colspan="1" rowspan="1" class="confluenceTh">Apache Geronimo (OpenEJB)</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Stateful and stateless Session Beans</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">BMP (Bean Managed Persistence) Entity Beans</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">CMP (Container Managed Persistence) Entity Beans</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceT
 d">Message driven beans (MDBs)</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Interoperability using RMI-IIOP or JAXRPC</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Ability to expose stateless session beans and MDBs as Web Services</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Support for sending and receiving messages via Web Services</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Easy provisioning and hot deployment of EJB a
 nd JMX-based Web Services</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">Access to EJBs from external CORBA objects</td><td colspan="1" rowspan="1" class="confluenceTd">supported</td><td colspan="1" rowspan="1" class="confluenceTd">supported</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.0.5</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Apache Geronimo (OpenEJB)</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Stateful and stateless Session Beans</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>BMP (Bean Managed Persistence) Entity Beans</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>CMP (Container Managed Persistence) Entity Beans</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" r
 owspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Message driven beans (MDBs)</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Interoperability using RMI-IIOP or JAXRPC</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Ability to expose stateless session beans and MDBs as Web Services</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Support for sending and receiving messages via Web Services</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p
 >supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Easy provisioning and hot deployment of EJB and JMX-based Web Services</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>Access to EJBs from external CORBA objects</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>supported</p></td></tr></tbody></table></div>
 
 
 <p><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Sampleapplication"></a>Sample application <a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-%23sample"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-SessionBeansMigration-Sampleapplication#sample">Sample application <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-SessionBeansMigration-#sample"></span></h1>
 
 <p>This is a simple eCommerce web site which sells computer related items in both retail and wholesale markets. To get the whole sale prices of items, customer has to buy at least given number of items. Otherwise he/she will get only retail prices of the item. End user of the application can add those items to their shopping cart. A stateless session bean has been used to manage the discount calculation business workflow activities while shopping cart of the application has been implemented with the help of a stateful session bean. </p>
 
 <p>The following figure illustrates the application flow:<br clear="none">
-<span class="image-wrap" style="display: block; text-align: center"><img src="jboss-to-geronimo-ejb-session-beans-migration.data/computer_overview.gif" style="border: 0px solid black"></span></p>
+<img class="confluence-embedded-image image-center" src="https://cwiki.apache.org/confluence/download/attachments/65033/computer_overview.gif?version=1&amp;modificationDate=1188899155000&amp;api=v2" data-image-src="/confluence/download/attachments/65033/computer_overview.gif?version=1&amp;modificationDate=1188899155000&amp;api=v2"></p>
 
 <p>A customer of this application directly login to the item list page. It will give all the details of the items they have currently on their stock. To buy one of these items in the stock, use the Buy link which comes with each item. It will forward customer in to the Add Item to Cart web page. To proceed buying, customer has to enter the quantity of items he/she needs. If this quantity exceeds the minimum discount quantity, discounts will be granted and added items in to the customer's shopping cart. Shopping cart web page displays the list of items already added to the cart and it enables removing of items from the cart. This application will be not allow to add the same item shopping cart twise. </p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-ApplicationclassesandJSPpages"></a>Application classes and JSP pages</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-ApplicationclassesandJSPpages">Application classes and JSP pages</h2>
 
 <ul><li>org.apache.geronimo.samples.computer.dto
 	<ul><li>ItemDTO - Data transfer object for item related information between web and ejb tiers.</li><li>TransactionDTO - Data transfer object for shopping cart transaction related information between web and ejb tiers.</li></ul>
@@ -150,20 +164,20 @@ A typical J2EE application may contain E
 <ul><li>buy_item.jsp -  Accepts quantity of items customer buys.</li><li>error.jsp - Display error conditions of the application.</li><li>index.jsp - Forward in to the item list of the application.</li><li>list_items.jsp - Display list of items in the stock.</li><li>shopping_cart.jsp - List of transactions added to the shopping cart will be displayed.</li></ul>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Toolsused"></a>Tools used</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-Toolsused">Tools used</h2>
 <p>The tools used for developing and building the Computer acessories seller application are:</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Eclipse"></a>Eclipse</h3>
+<h3 id="JBosstoGeronimo-EJB-SessionBeansMigration-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-EJB-SessionBeansMigration-ApacheAnt"></a>Apache Ant</h3>
+<h3 id="JBosstoGeronimo-EJB-SessionBeansMigration-ApacheAnt">Apache Ant</h3>
 <p>Ant is a pure Java build tool. It is used for building the war files and populating the database for the Online Brokerage 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-EJB-SessionBeansMigration-top">Back to Top</a></p>
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-TheJBossenviroment"></a>The JBoss enviroment <a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-%23jboss"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-SessionBeansMigration-TheJBossenviroment#jboss">The JBoss enviroment <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-SessionBeansMigration-#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. Note that for this migration example JBoss v4.0.5 was used.</p>
 
@@ -171,37 +185,37 @@ A typical J2EE application may contain E
 
 <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.0.5 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.0.5 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 <b>run.sh -c &lt;your_server_name&gt;</b> 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 step is described in the following section.</li></ol>
+<ol><li>Download and install JBoss v4.0.5 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.0.5 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 <strong>run.sh -c &lt;your_server_name&gt;</strong> 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 prerequi
 site software required by the sample application. This step is described in the following section.</li></ol>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Installandconfigureprerequisitesoftware"></a>Install and configure prerequisite software</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-Installandconfigureprerequisitesoftware">Install and configure prerequisite software</h2>
 <p>In order to build and run this sample application included in this article, you need to install and configure the Ant build tool.</p>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-ConfigureAnt"></a>Configure Ant</h3>
+<h3 id="JBosstoGeronimo-EJB-SessionBeansMigration-ConfigureAnt">Configure Ant</h3>
 
-<p>As mentioned before, Apache Ant is used to build the binaries for the Online Brokerage 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 Online Brokerage 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>
 
-<h3><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-ConfigureXDoclet"></a>Configure XDoclet</h3>
+<h3 id="JBosstoGeronimo-EJB-SessionBeansMigration-ConfigureXDoclet">Configure XDoclet</h3>
 
 <p>XDoclet is going to be used as build tool for the configuration file generation. It  is an open source code generation engine. It enables Attribute-Oriented Programming for java. In short, this means that you can add more significance to your code by adding meta data (attributes) to your java sources. This is done in special JavaDoc tags.<br clear="none">
 Although XDoclet originated as a tool for creating EJBs, it has evolved into a general-purpose code generation engine. XDoclet consists of a core and a constantly growing number of modules. It is fairly straight forward to write new modules if there is a need for a new kind of component.<br clear="none">
 <a shape="rect" class="external-link" href="http://xdoclet.sourceforge.net/xdoclet/index.html" rel="nofollow">http://xdoclet.sourceforge.net/xdoclet/index.html</a></p>
 
-<p>Just extract the latest version of the XDoclet and set the <b>xdoclet.home</b> parameter in to the <b>build.properties</b> file.</p>
+<p>Just extract the latest version of the XDoclet and set the <strong>xdoclet.home</strong> parameter in to the <strong>build.properties</strong> file.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Buildthesampleapplication"></a>Build the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-Buildthesampleapplication">Build the sample application</h2>
 
 <p>The computer acessories selling application included with this article provides an Ant script that you will use in order to build the application. Download the computer acessories selling application from the following link:</p>
 
-<p><a shape="rect" href="jboss-to-geronimo-ejb-session-beans-migration.data/computer.zip?version=1&amp;modificationDate=1188899105000">Computer</a></p>
+<p><a shape="rect" href="jboss-to-geronimo-ejb-session-beans-migration.data/computer.zip?version=1&amp;modificationDate=1188899105000&amp;api=v2">Computer</a></p>
 
-<p>After extracting the zip file, a <b>computer</b> directory is created. In that directory open the build.properties file and edit the properties to match your environment as shown in the following example:</p>
+<p>After extracting the zip file, a <strong>computer</strong> directory is created. In that directory open the build.properties file and edit the properties to match your environment as 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>build.properties</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.properties</b></div><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
 ## Set the Geronimo 1.1 home here
 geronimo.home=&lt;geronimo_home&gt;
@@ -211,18 +225,18 @@ xdoclet.home=&lt;xdoclet_home&gt;
 ]]></script>
 </div></div>
 
-<p>Before starting the build process just set the correct paths for the <b>geronimo.home</b> and <b>xdoclet.home</b> entries in the <b>build.properties</b> file in the <b>config</b> directory.</p>
+<p>Before starting the build process just set the correct paths for the <strong>geronimo.home</strong> and <strong>xdoclet.home</strong> entries in the <strong>build.properties</strong> file in the <strong>config</strong> directory.</p>
 
-<p>From a command prompt or shell go to the <b>computer</b> directory and run <b>ant jboss</b>. This will build the ear file and place it directly in the <b>releases/jboss</b> directory.</p>
+<p>From a command prompt or shell go to the <strong>computer</strong> directory and run <strong>ant jboss</strong>. This will build the ear file and place it directly in the <strong>releases/jboss</strong> directory.</p>
 
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Deploythesampleapplication"></a>Deploy the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-Deploythesampleapplication">Deploy the sample application</h2>
 
-<p>To deploy the sample application just copy the <b>computer.ear</b> will be created under the <b>computer/releases/jboss</b> folder to the <b>&lt;jboss_home&gt;/server/&lt;your_server_name&gt;/deploy</b> folder. </p>
+<p>To deploy the sample application just copy the <strong>computer.ear</strong> will be created under the <strong>computer/releases/jboss</strong> folder to the <strong>&lt;jboss_home&gt;/server/&lt;your_server_name&gt;/deploy</strong> folder. </p>
 
 <p>If JBoss is already started, it will automatically deploy and start the application; otherwise, the application will be deployed and started at the next startup.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Testthesampleapplication"></a>Test the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-Testthesampleapplication">Test the sample application</h2>
 
 <p>To test the application, open a Web browser and access the following URL:</p>
 
@@ -230,34 +244,42 @@ xdoclet.home=&lt;xdoclet_home&gt;
 
 <p>This brings up the item list page of the computer acessories selling application. You can buy computer acessories using this application. The application is now configured and running.</p>
 
-<p><span class="image-wrap" style="display: block; text-align: center"><img src="jboss-to-geronimo-ejb-session-beans-migration.data/Computer_screen.gif" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image image-center" src="https://cwiki.apache.org/confluence/download/attachments/65033/Computer_screen.gif?version=1&amp;modificationDate=1188899155000&amp;api=v2" data-image-src="/confluence/download/attachments/65033/Computer_screen.gif?version=1&amp;modificationDate=1188899155000&amp;api=v2"></p>
 
 <p>Following is the demonstration of a shopping cart of the sample application.</p>
 
-<p><span class="image-wrap" style="display: block; text-align: center"><img src="jboss-to-geronimo-ejb-session-beans-migration.data/shopping_cart.gif" style="border: 0px solid black"></span></p>
+<p><img class="confluence-embedded-image image-center" src="https://cwiki.apache.org/confluence/download/attachments/65033/shopping_cart.gif?version=1&amp;modificationDate=1188899155000&amp;api=v2" data-image-src="/confluence/download/attachments/65033/shopping_cart.gif?version=1&amp;modificationDate=1188899155000&amp;api=v2"></p>
 
 <p><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-top">Back to Top</a></p>
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-TheGeronimoenviroment"></a>The Geronimo enviroment <a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-%23geronimo"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-SessionBeansMigration-TheGeronimoenviroment#geronimo">The Geronimo enviroment <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-SessionBeansMigration-#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-EJB-SessionBeansMigration-top">Back to Top</a></p>
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Stepbystepmigration"></a>Step-by-step migration <a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-%23migration"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-SessionBeansMigration-Step-by-stepmigration#migration">Step-by-step migration <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-SessionBeansMigration-#migration"></span></h1>
 
-<p>When you built the computer acessories selling sample application, Ant packaged the deployment descriptors for both JBoss <b>jboss.xml</b> and Geronimo <b>openejb-jar.xml</b> as they were already provided by the sample application. These files are located in the <b>computer/config</b> directory.</p>
+<p>When you built the computer acessories selling sample application, Ant packaged the deployment descriptors for both JBoss <strong>jboss.xml</strong> and Geronimo <strong>openejb-jar.xml</strong> as they were already provided by the sample application. These files are located in the <strong>computer/config</strong> directory.</p>
 
 <p>The following example shows the JBoss deployment descriptor.</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.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.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;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 
 &lt;jboss&gt;
 
@@ -289,11 +311,11 @@ xdoclet.home=&lt;xdoclet_home&gt;
 
 <p>Compare it with the contents of the Geronimo deployment plan 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>openejb-jar.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>openejb-jar.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;openejb-jar xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1"&gt;
-	&lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
+&lt;openejb-jar xmlns=&quot;http://www.openejb.org/xml/ns/openejb-jar-2.1&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;org.apache.geronimo.samples&lt;/dep:groupId&gt;
 			&lt;dep:artifactId&gt;ComputerEJB&lt;/dep:artifactId&gt;
@@ -320,13 +342,13 @@ xdoclet.home=&lt;xdoclet_home&gt;
 ]]></script>
 </div></div>
 
-<p>First difference can be clearly noted is Geronimo specific configuration has more additional information than JBoss specific one. That part of the Geronimo configuration file is quite similar to a Maven 2 build script. Both of these given configuration files has EJB information. JBoss uses local JNDI names to link their EJBs while Geronimo directly use EJB's name. In addition to above differences also <b>openejb-jar.xml</b> file clearly gives the ejb reference information than <b>jboss.xml</b> file. </p>
+<p>First difference can be clearly noted is Geronimo specific configuration has more additional information than JBoss specific one. That part of the Geronimo configuration file is quite similar to a Maven 2 build script. Both of these given configuration files has EJB information. JBoss uses local JNDI names to link their EJBs while Geronimo directly use EJB's name. In addition to above differences also <strong>openejb-jar.xml</strong> file clearly gives the ejb reference information than <strong>jboss.xml</strong> file. </p>
 
 <p>Looking at the web archive related configuration files give you few more differnces.</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-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>jboss-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;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
 &lt;jboss-web&gt;
 
   &lt;!-- EJB Local References --&gt;
@@ -342,11 +364,11 @@ xdoclet.home=&lt;xdoclet_home&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>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-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 xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1" xmlns:naming="http://geronimo.apache.org/xml/ns/naming-1.1"&gt;
-  &lt;dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1"&gt;
+&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&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;&gt;
+  &lt;dep:environment xmlns:dep=&quot;http://geronimo.apache.org/xml/ns/deployment-1.1&quot;&gt;
     &lt;dep:moduleId&gt;
       &lt;dep:groupId&gt;org.apache.geronimo.samples&lt;/dep:groupId&gt;
       &lt;dep:artifactId&gt;ComputerWeb&lt;/dep:artifactId&gt;
@@ -371,20 +393,20 @@ xdoclet.home=&lt;xdoclet_home&gt;
 ]]></script>
 </div></div>
 
-<p><b>jboss-web.xml</b> map the EJBs from their JNDI names as given the above while <b>geronimo-web.xml</b> uses directly EJB's name. The reference names given in each mapping will be used refer EJBs from the Servlets. <b>web.xml</b> file of the WAR file contains more information about each EJB reference name, which will be common to the both Geronimo and JBoss flavours of this application.</p>
+<p><strong>jboss-web.xml</strong> map the EJBs from their JNDI names as given the above while <strong>geronimo-web.xml</strong> uses directly EJB's name. The reference names given in each mapping will be used refer EJBs from the Servlets. <strong>web.xml</strong> file of the WAR file contains more information about each EJB reference name, which will be common to the both Geronimo and JBoss flavours of this application.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Buildthesampleapplication"></a>Build the sample application</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-Buildthesampleapplication.1">Build the sample application</h2>
 
-<p>Build the migrated Geronimo version of the sample application by running following command from the <b>computer</b> directory.<br clear="none">
-<b>ant geronimo</b><br clear="none">
-It will create <b>computer.ear</b> file in the <b>computer/releases/geronimo</b> folder.</p>
+<p>Build the migrated Geronimo version of the sample application by running following command from the <strong>computer</strong> directory.<br clear="none">
+<strong>ant geronimo</strong><br clear="none">
+It will create <strong>computer.ear</strong> file in the <strong>computer/releases/geronimo</strong> folder.</p>
 
-<h2><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Deploythemigratedapplication"></a>Deploy the migrated application</h2>
+<h2 id="JBosstoGeronimo-EJB-SessionBeansMigration-Deploythemigratedapplication">Deploy the migrated application</h2>
 
 <p>To deploy the migrated Computer acessories selling application, make sure the Geronimo server is up and running.</p>
 
 <p>Open Geronimo console in your browser and follow the given steps:</p>
-<ol><li>Travel <b>Deploy New</b> from the <b>Console Navigation</b>.</li><li>Load <b>computer.ear</b> from <b>computer/releases/geronimo</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>Travel <strong>Deploy New</strong> from the <strong>Console Navigation</strong>.</li><li>Load <strong>computer.ear</strong> from <strong>computer/releases/geronimo</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>
 
 
 <p>Once the application is deployed, open a Web browser and access the following URL:<br clear="none">
@@ -392,13 +414,12 @@ It will create <b>computer.ear</b> file 
 
 <p><a shape="rect" href="#JBosstoGeronimo-EJB-SessionBeansMigration-top">Back to Top</a></p>
 
-<h1><a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-Summary"></a>Summary <a shape="rect" name="JBosstoGeronimo-EJB-SessionBeansMigration-%23summary"></a></h1>
+<h1 id="JBosstoGeronimo-EJB-SessionBeansMigration-Summary#summary">Summary <span class="confluence-anchor-link" id="JBosstoGeronimo-EJB-SessionBeansMigration-#summary"></span></h1>
 <p>This article has shown how to migrate a sample application that uses Session Beans, from JBoss v4.0.5 to Apache Geronimo. This article provided step-by-step instructions to build the application, deploy and run it, and then migrate it to the Geronimo environment.</p>
 
 <p>The following list summarizes the major differences found during this sample application migration.</p>
 
-<ul><li>In order to deploy an EJB jar file in JBoss you need to just copy the configuration file to the deploy directory but in Geronimo you can use either deployer tool, console or hot deployment directory.</li><li>The contents of the deployment plans for EJB jar files in JBoss and in Geronimo are almost similar except for the starting part of the Geronimo which is more similar to a Maven 2 build file.</li></ul>
-</div>
+<ul><li>In order to deploy an EJB jar file in JBoss you need to just copy the configuration file to the deploy directory but in Geronimo you can use either deployer tool, console or hot deployment directory.</li><li>The contents of the deployment plans for EJB jar files in JBoss and in Geronimo are almost similar except for the starting part of the Geronimo which is more similar to a Maven 2 build file.</li></ul></div>
         </div>
 
         



Mime
View raw message