[jbosstools-commits] JBoss Tools SVN: r7087 - trunk/seam/docs/reference/en/modules.
jbosstools-commits at lists.jboss.org
jbosstools-commits at lists.jboss.org
Mon Mar 24 12:03:00 EDT 2008
Author: ykryvinchanka
Date: 2008-03-24 12:03:00 -0400 (Mon, 24 Mar 2008)
New Revision: 7087
Modified:
trunk/seam/docs/reference/en/modules/directory_structure.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-135 relative link's been added
Modified: trunk/seam/docs/reference/en/modules/directory_structure.xml
===================================================================
--- trunk/seam/docs/reference/en/modules/directory_structure.xml 2008-03-24 15:58:02 UTC (rev 7086)
+++ trunk/seam/docs/reference/en/modules/directory_structure.xml 2008-03-24 16:03:00 UTC (rev 7087)
@@ -6,59 +6,73 @@
<keyword>JBoss Tools</keyword>
<keyword>Seam</keyword>
<keyword>Eclipse</keyword>
- </keywordset>
+ </keywordset>
</chapterinfo>
-
+
<title>Directory Structure of the Generated Project</title>
-
- <para>In this chapter we describe where the Seam wizard puts the generated files for both EAR and WAR deployments.</para>
- <para>The Seam Project wizard generates projects like Eclipse WTP style in order to utilize Eclipse WTP features and to have a correct classpath. To be more precise it generates
- one project per artifact.</para>
-
- <section id="WAR">
+
+ <para>In this chapter we describe where the Seam wizard puts the generated files for both EAR
+ and WAR deployments.</para>
+ <para>The Seam Project wizard generates projects like Eclipse WTP style in order to utilize
+ Eclipse WTP features and to have a correct classpath. To be more precise it generates one
+ project per artifact.</para>
+
+ <section id="WAR">
<title>WAR Deployment</title>
-
- <para>The project layout for WAR projects is:</para>
-
- <figure>
- <title>Project Layout for WAR projects</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/directory_structure/directory_structure_1.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>A WAR project can only use Seam JavaBean and JPA Entity bean components; it cannot use EJB3 Session beans etc.</para>
- <para>WAR projects are generated to enable Seam 1.2.1 war hotdeploy feature. Classes put into <emphasis><property>src/action</property></emphasis> will be
- deployed to <emphasis><property>WEB-INF/dev</property></emphasis> from which Seam 1.2.1 automatically will perform hotdeploy of new components.</para>
- <note>
- <title>Note:</title>
- <para>Because of Eclipse WTP limits the hot deployed classes also existed in <emphasis><property>WEB-INF/classes</property></emphasis>,
- but since Seam gives <emphasis><property>WEB-INF/dev</property></emphasis> precedence it will work.</para>
- </note>
-
- <para>Furthermore the Seam Project wizard generates a test project that is setup to run TestNG directly against the proper libraries and server runtime libraries.
- When the TestNG plugin is installed you can just run your tests via <emphasis><property>Run As > TestNG Test</property>.</emphasis></para>
-
+
+ <para>The project layout for WAR projects is:</para>
+
+ <figure>
+ <title>Project Layout for WAR projects</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/directory_structure/directory_structure_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>A WAR project can only use Seam JavaBean and JPA Entity bean components; it cannot use
+ EJB3 Session beans etc.</para>
+ <para>WAR projects are generated to enable Seam 1.2.1 war hotdeploy feature. Classes put
+ into <emphasis>
+ <property>src/action</property>
+ </emphasis> will be deployed to <emphasis>
+ <property>WEB-INF/dev</property>
+ </emphasis> from which Seam 1.2.1 automatically will perform hotdeploy of new
+ components.</para>
+ <note>
+ <title>Note:</title>
+ <para>Because of Eclipse WTP limits the hot deployed classes also existed in <emphasis>
+ <property>WEB-INF/classes</property>
+ </emphasis>, but since Seam gives <emphasis>
+ <property>WEB-INF/dev</property>
+ </emphasis> precedence it will work.</para>
+ </note>
+
+ <para>Furthermore the Seam Project wizard generates a test project that is setup to run
+ <link linkend="testNG">TestNG</link> directly against the proper libraries and
+ server runtime libraries. When the TestNG plugin is installed you can just run your
+ tests via <emphasis><property>Run As > TestNG Test</property>.</emphasis></para>
+
</section>
-
- <section id="EAR">
+
+ <section id="EAR">
<title>EAR Deployment</title>
- <para>The project layout for EAR projects is:</para>
-
- <figure>
- <title>Project Layout for WAR projects</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/directory_structure/directory_structure_2.png" />
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>An EAR project can use the whole range of Seam components, including EJB3 Session beans.</para>
-
+ <para>The project layout for EAR projects is:</para>
+
+ <figure>
+ <title>Project Layout for WAR projects</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/directory_structure/directory_structure_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>An EAR project can use the whole range of Seam components, including EJB3 Session
+ beans.</para>
+
</section>
-
-
- </chapter>
+
+
+</chapter>
More information about the jbosstools-commits
mailing list