[seam-commits] Seam SVN: r11665 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

seam-commits at lists.jboss.org seam-commits at lists.jboss.org
Tue Nov 24 00:55:25 EST 2009


Author: laubai
Date: 2009-11-24 00:55:24 -0500 (Tue, 24 Nov 2009)
New Revision: 11665

Modified:
   tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
Log:
Edited Migration chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml	2009-11-24 05:27:45 UTC (rev 11664)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Migration.xml	2009-11-24 05:55:24 UTC (rev 11665)
@@ -11,13 +11,13 @@
       is to create a new project using seam-gen in Seam 2, and migrate your code
       across. We recognize that many projects may have extensive customizations
       to their project, so we also provide instructions for how to upgrade your
-      project in-situ in <xref linkend="migrating.insitu" /> Due to the number 
+      project in-situ in <xref linkend="migrating.insitu" />. Due to the number 
       of changes introduced between Seam 1.2 and Seam 2, this may not always be 
       a straightforward process! 
    </para>
    
    <para>
-      However you decide to migrate your application, you'll need to alter your
+      However you decide to migrate your application, you will need to alter your
       code, as many components have moved. <xref linkend="migrating.general"/>
       details those changes.
    </para>
@@ -26,7 +26,7 @@
       <title>Creating a new project skeleton using seam-gen</title>
       
       <para>
-         Start by creating a new skeleton seam project. In your Seam 2
+         Start by creating a new skeleton Seam project. In your Seam 2
          directory run:
       </para>
       
@@ -34,7 +34,7 @@
       
       <para>
          Customize the defaults as needed. You'll want to set the location of 
-         JBoss EAP, name your project and select an EAR or WAR as needed; you 
+         JBoss Enterprise Application Platform, name your project and select an EAR or WAR as needed; you 
          can accept the defaults for Java package names (as we aren't going to
          use the reverse engineering features of seam-gen); you'll want to set
          your JDBC driver, URL, username and password correctly, and configure
@@ -69,13 +69,13 @@
          <warning>
             <para>
                You only need to do this if you are migrating from the community
-               edition of Seam, JBoss EAP 4.2 and 4.3 shipped a version of Seam
+               edition of Seam. JBoss Enterprise Application Platform 4.2 and 4.3 shipped a version of Seam
                1.2 which used JSF 1.2.
             </para>
          </warning>
          
          <para>
-            Seam 2.0 requires JSF 1.2, and JBoss EAP supports Sun's JSF RI. To 
+            Seam 2.0 requires JSF 1.2, and JBoss Enterprise Application Platform supports Sun's JSF RI. To 
             switch to JSF 1.2, you need to remove the MyFaces listener:
          </para>
          
@@ -117,8 +117,8 @@
 </web-app>]]></programlisting> 
          
          <para>
-            In your Seam 1.2 app you may have specified some Seam specific 
-            configuration in <literal>web.xml</literal>.  First, we'll discuss
+            In your Seam 1.2 application you may have specified some Seam specific 
+            configuration in <literal>web.xml</literal>. First, we'll discuss
             all the Seam related elements you need in 
             <literal>web.xml</literal>, not just those that have changed, noting
             any changes.
@@ -134,8 +134,7 @@
 </listener>]]></programlisting>
 
          <para>
-            Modify the Seam master filter (note the package of the class 
-            changed):
+            Modify the Seam master filter (note the change to the class package):
          </para>
          
          <programlisting role="XML"><![CDATA[<filter>
@@ -170,7 +169,7 @@
 </servlet-mapping>]]></programlisting>
          
          <para>
-            Seam 2 will automatically install RichFaces' Ajax4JSF if it present
+            Seam 2 will automatically install RichFaces Ajax4JSF if it present
             in your project so you should make sure the Ajax4JSF filter isn't
             declared:
          </para>
@@ -295,7 +294,7 @@
          </para>
 
          <para>
-            For testing, you need the jars in Seam's <literal>lib/test</literal>,
+            For testing, you need the jars in Seam's <literal>lib/test</literal> directory,
             the jars in Seam's <literal>lib/</literal> directory, your test 
             classes and application classes together with the 
             <literal>bootstrap/</literal> directory in your classpath. 
@@ -341,7 +340,7 @@
       
       <important>
          <para>
-            Don't forget to update the XSD's in <literal>pages.xml</literal> and
+            Don't forget to update the XSDs in <literal>pages.xml</literal> and
             <literal>components.xml</literal> to point at the ones for Seam 2.
             Just change the suffix from <literal>-1.2.xsd</literal> to
             <literal>-2.0.xsd</literal>.
@@ -353,7 +352,7 @@
          
          <para>
             Seam's built-in components have undergone a major reorganization 
-            designed to organize them for easier learning, and to isolate 
+            designed to make them easier to learn, and to isolate 
             dependencies upon particular technologies like JSF into specific 
             packages.
          </para>
@@ -406,13 +405,13 @@
             </listitem>
             <listitem>
                <para>
-                  The Pageflow component are located in 
+                  The Pageflow components are located in 
                   <literal>org.jboss.seam.pageflow</literal>
                </para>
             </listitem>
             <listitem>
                <para>
-                  The Pages component are located in 
+                  The Pages components are located in 
                   <literal>org.jboss.seam.navigation</literal>
                </para>
             </listitem>
@@ -1047,7 +1046,7 @@
          <title>Annotation changes in Seam 2</title>
          
          <para>
-            Annotations have also moved to reflect their purpose. In
+            Annotations have also moved to reflect their purpose.
          </para>
          
          <itemizedlist>
@@ -1209,7 +1208,7 @@
             </listitem>
             <listitem>
                <para>
-                  Exception handling annotations moved to 
+                  Annotations related to exception handling have moved to 
                   <literal>org.jboss.seam.annotations.exception</literal>
                </para>
                <itemizedlist>
@@ -1284,7 +1283,7 @@
 
          <para>
             If you are using jBPM for business processes, 
-            you need to add the tx service to <literal>jbpm.cfg.xml</literal>:
+            you need to add the <classname>tx</classname> service to <literal>jbpm.cfg.xml</literal>:
          </para>
          
          <programlisting role="XML"><![CDATA[<service name="tx" factory="org.jbpm.tx.TxServiceFactory" />]]></programlisting> 
@@ -1318,7 +1317,7 @@
 		to the data picker from your stylesheet to save on unnecessary bandwidth use.
          </para>
          <para>
-            You should check the RichFaces documentation for more information on
+            Check the RichFaces documentation for more information on
             parameter name changes and namespace changes.
          </para>
          
@@ -1354,7 +1353,7 @@
       	<title>Changes to seam-gen</title>
       	
       	<para>There was a change in seam-gen regarding
-		how the generated classes are organized when generate-entities is
+		how generated classes are organized when generate-entities is
 		executed.</para>
 
 		<variablelist>		



More information about the seam-commits mailing list