[jboss-cvs] JBossAS SVN: r105541 - projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Jun 1 23:47:22 EDT 2010
Author: misty at redhat.com
Date: 2010-06-01 23:47:22 -0400 (Tue, 01 Jun 2010)
New Revision: 105541
Modified:
projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Gettingstarted.xml
Log:
JBPAPP-4387
Modified: projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Gettingstarted.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Gettingstarted.xml 2010-06-02 03:41:35 UTC (rev 105540)
+++ projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Gettingstarted.xml 2010-06-02 03:47:22 UTC (rev 105541)
@@ -22,14 +22,14 @@
JBoss has sophisticated support for hot redeployment of <filename>WAR</filename>s and <filename>EAR</filename>s. Unfortunately, due to bugs in JVM, repeat redeployment of an EAR (common during development) uses all of the JVM's perm gen space. Therefore, we recommend running JBoss in a JVM with a large perm gen space during development. If you are running JBoss from JBoss IDE, you can configure this in the server launch configuration, under "VM arguments". We suggest the following values:
</para>
-<programlisting>-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m
-</programlisting>
+<screen>-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m
+</screen>
<para>
The minimum recommended values are:
</para>
-<programlisting>-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m
-</programlisting>
+<screen>-Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256m
+</screen>
<para>
If you are running JBoss from the command line, you can configure the JVM options in <filename>bin/run.conf</filename>.
</para>
@@ -41,12 +41,11 @@
First, configure seam-gen for your environment. Just type the following in your command line interface:
</para>
-<programlisting>cd <seam_distribution_dir> seam setup</programlisting>
+<command>cd <replaceable>seam_distribution_dir</replaceable>; seam setup</command>
<para>
You will receive the following prompt for the required information:
</para>
-
-<programlisting><seam_distribution_dir>$ ./seam setup
+<screen>
Buildfile: build.xml
init:
@@ -100,7 +99,7 @@
BUILD SUCCESSFUL
Total time: 1 minute 32 seconds
~/workspace/jboss-seam $
-</programlisting>
+</screen>
<para>
The tool provides sensible defaults. To accept them, press <keycap>Enter</keycap> when prompted.
</para>
@@ -114,10 +113,9 @@
Create a new project in our Eclipse workspace directory by typing:
</para>
-<programlisting>seam new-project
-</programlisting>
-
-<programlisting><seam_distribution_dir> seam new-project
+<command>seam new-project</command>
+
+<screen>
Buildfile: build.xml
...
new-project:
@@ -127,7 +125,7 @@
[echo] NetBeans Users: Open the project in NetBeans
BUILD SUCCESSFUL Total time: 7 seconds
C:\Projects\jboss-seam>
-</programlisting>
+</screen>
<para>
This copies the Seam <filename>JAR</filename>s, dependent <filename>JAR</filename>s and the JDBC driver <filename>JAR</filename> to a new Eclipse project. It generates all required resources and configuration files, a Facelets template file and stylesheet, along with Eclipse metadata and an Ant build script. The Eclipse project will be automatically deployed to an exploded directory structure in JBoss as soon as you add the project. To add the project, go to <guimenu>New</guimenu> → <guimenu>Project...</guimenu> → <guimenu>General</guimenu> → <guimenu>Project</guimenu> → <guimenu>Next</guimenu>, type the <guilabel>Project name</guilabel> (in this case, <literal>helloworld</literal>), and then click <literal>Finish</literal>. Do not select <literal>Java Project</literal> from the New Project wizard.
</para>
@@ -154,13 +152,12 @@
You can create a simple web page with a stateless action method by typing:
</para>
-<programlisting>seam new-action
-</programlisting>
+<command>seam new-action</command>
<para>
Seam prompts for some information, and generates a new Facelets page and Seam component for your project.
</para>
-<programlisting>C:\Projects\jboss-seam>seam new-action
+<screen>
Buildfile: build.xml
validate-workspace:
@@ -193,7 +190,7 @@
BUILD SUCCESSFUL
Total time: 13 seconds
C:\Projects\jboss-seam>
-</programlisting>
+</screen>
<para>
Since we have added a new Seam component, it is necessary to restart the exploded directory deployment. You can do this by typing <literal>seam restart</literal>, or by running the <literal>restart</literal> target in the generated project's <literal>build.xml</literal> file from within Eclipse. Alternatively, you can edit the <literal>resources/META-INF/application.xml</literal> file in Eclipse.
</para>
@@ -216,10 +213,8 @@
The next step is to create a form. Type:
</para>
-<programlisting>seam new-form
-</programlisting>
-
-<programlisting>C:\Projects\jboss-seam>seam new-form
+<command>seam new-form</command>
+<screen>
Buildfile: C:\Projects\jboss-seam\seam-gen\build.xml
validate-workspace:
@@ -252,7 +247,7 @@
BUILD SUCCESSFUL
Total time: 5 seconds
C:\Projects\jboss-seam>
-</programlisting>
+</screen>
<para>
Restart the application again, and go to <literal>http://localhost:8080/helloworld/hello.seam</literal>. Look at the generated code. Run the test. Experiment with adding new fields to the form and Seam component. (Remember to restart the deployment each time you alter the Java code.)
</para>
@@ -264,8 +259,7 @@
Manually create tables in your database. (To switch to a different database, run <literal>seam setup</literal> again.) Now type:
</para>
-<programlisting>seam generate-entities
-</programlisting>
+<command>seam generate-entities</command>
<para>
Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>. You can browse the database, edit existing objects, and create new objects. The code generated here is very simple. Seam was designed so that data access code is easy to write by hand, even without the assistance of seam-gen.
</para>
@@ -277,8 +271,8 @@
Place your existing, valid entity classes inside the <literal>src/main</literal> directory. Now, type:
</para>
-<programlisting>seam generate-ui
-</programlisting>
+<command>seam generate-ui</command>
+
<para>
Restart the deployment, and go to <literal>http://localhost:8080/helloworld</literal>.
</para>
@@ -293,8 +287,8 @@
By default, the application deploys with the <emphasis>dev profile</emphasis>. The EAR includes the <filename>persistence-dev.xml</filename> and <filename>import-dev.sql</filename> files, and deploys <filename>myproject-dev-ds.xml</filename>. You can change the profile to <emphasis>prod profile</emphasis> by typing:
</para>
-<programlisting>seam -Dprofile=prod deploy
-</programlisting>
+<command>seam -Dprofile=prod deploy</command>
+
<para>
You can also define new deployment profiles for your application. Just add appropriately named files to your project — for example, <filename>persistence-staging.xml</filename>, <filename>import-staging.sql</filename> and <filename>myproject-staging-ds.xml</filename> — and select the name of the profile with <literal>-Dprofile=staging</literal>.
</para>
@@ -306,7 +300,7 @@
Some support for incremental hot deployment is included during development when you deploy your Seam application as an exploded directory. Add the following line to <filename>components.xml</filename> to enable debug mode in Seam and Facelets:
</para>
-<programlisting role="XML"><![CDATA[<core:init debug="true">]]>
+<programlisting language="XML" role="XML"><![CDATA[<core:init debug="true">]]>
</programlisting>
<para>
The following files may now be redeployed without requiring a full restart of the web application:
More information about the jboss-cvs-commits
mailing list