Author: ochikvina Date: 2008-01-21 12:01:38 -0500 (Mon, 21 Jan 2008) New Revision: 5843 Modified: trunk/as/docs/reference/en/modules/webtools.xml Log: http://jira.jboss.com/jira/browse/JBDS-199 - renaming sections and rearranging some data Modified: trunk/as/docs/reference/en/modules/webtools.xml =================================================================== --- trunk/as/docs/reference/en/modules/webtools.xml 2008-01-21 17:00:58 UTC (rev 5842) +++ trunk/as/docs/reference/en/modules/webtools.xml 2008-01-21 17:01:38 UTC (rev 5843) @@ -1,81 +1,90 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="webtools"> - <title>WTP Projects</title> - <para>This chapter covers how to select installed runtime/server in your web project</para> + <title>Projects</title> + <para>The most popular of the projects we deal with are the J2EE projects, such as + <property>Dynamic Web Project</property>, EJB Project, or EAR project. Web projects of + JBoss Tools are Stuts, JSF and Seam projects. In this chapter we are going to tell you about + facets the main benefit of which to provide proper structuring and packaging for any type of + project.</para> - <section><title>Description</title> - <para> - WTP provides what are called "faceted" projects. - Their most popular of these projects are their J2EE projects, - such as their <property>Dynamic Web Project</property>, their EJB Project, - or their EAR project. Web projects of JBoss Tools are Stuts, JSF and Seam projects.</para> - <para> - The idea behind faceted projects is that each project - can accept units of functionality, or facets, which can be - added or removed by the user. Some examples of these facets - are adding a webdoclet facet to a web project, or an - ejbdoclet to an EJB Project. </para> - <para> - Most often, these "facets" either add to the project's classpath, - enable a builder, or watch the project in some other fashion. </para> - <para> - WTP projects have undergone some criticism as being - <emphasis>over-engineered</emphasis> or too restrictive in their - design. WTP projects are set up in a tree-relationship to each other, - where one project can be a child of another. For example, an EAR - project may have a Web Project child, an EJB project child, - or other types. </para> - <para> - The benefit of this is that the structure of your projects is - then known, and packaging it up *should* be trivial. However, - if your project is non-standard, or you feel too confined by - such rigid structural requirements, you can still choose to - package your project using the Archives plugin</para> + <section> + <title>Description</title> + <para>The idea behind faceted projects is that each project can accept units of + functionality, or facets, which can be added or removed by the user. Some examples of + these facets are adding a webdoclet facet to a web project, or an ejbdoclet to an EJB + Project. </para> + <para> Most often, these "facets" either add to the project's classpath, enable a builder, + or watch the project in some other fashion. </para> + <para> WTP projects have undergone some criticism as being + <emphasis>over-engineered</emphasis> or too restrictive in their design. WTP projects + are set up in a tree-relationship to each other, where one project can be a child of + another. For example, an EAR project may have a Web Project child, an EJB project child, + or other types. </para> + <para> The benefit of this is that the structure of your projects is then known, and + packaging it up *should* be trivial. However, if your project is non-standard, or you + feel too confined by such rigid structural requirements, you can still choose to package + your project using the Archives plugin.</para> - </section> - - - <section><title>Faceted Project Wizards</title> - <para>To create a new <property>Dynamic Web Project</property> select <emphasis><property>File &gt; New &gt; Other...</property></emphasis> then <emphasis><property>Web &gt; Dynamic Web Project</property></emphasis></para> - <figure> - <title>New Dynamic Web Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/webtools/webtools_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Click <emphasis><property>Next</property></emphasis> and you will see Dynamic Web Project page</para> - <figure> - <title>Faceted Project Wizard: First Page</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/webtools/webtools_2.png"/> - </imageobject> - </mediaobject> - </figure> - <para> - The first page of most WTP projects allows you to target a specific runtime, - representing a server's library location. It will also provide you the ability to - add this project to an EAR project, and select a pre-selected default set of facets, - called a configuration, rather than manually select each facet you might want.</para> - <para> - Selecting the runtime, again, allows the project to install the proper - classpaths to the project so it knows what code to compile against.</para> - <figure> - <title>Faceted Project Wizard: Second Page</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/webtools/webtools_3.png"/> - </imageobject> - </mediaobject> - </figure> - <para> - The second page of the wizard allows you to enable or disable specific facets, as - described above. Some facets may require others, and some may conflict with others, - but on the whole this page allows you to add any number of facets that don't conflict - with each other. </para> - <para> - Further pages are specific to either the project type, or the facets selected.</para> - </section> -</chapter> + </section> + + + <section> + <title>Adding Facets to a Project</title> + + <para>There are two ways to add facets to a project. The first way is to include facets into + already existing project. For that you should bring up the context menu for selected + project and click <emphasis> + <property>Properties</property> + </emphasis>. At this point, choose <emphasis> + <property>Project Facets</property> + </emphasis> from the left. It will represent a list of the facets for your project and + give opportunity to modify it by clicking on <emphasis> + <property>Modify Project...</property> + </emphasis> button.</para> + + <para>The other way is adding necessary facets while organizing a new project. To demonstrate + it let&apos;s create a new <property>Dynamic Web Project</property> selecting as usual <emphasis> + <property>File &gt; New &gt; Other...</property> + </emphasis> and then <emphasis> + <property>Web &gt; Dynamic Web Project.</property> + </emphasis></para> + <figure> + <title>New Dynamic Web Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/webtools/webtools_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click <emphasis> + <property>Next</property> + </emphasis> and you will see Dynamic Web Project page.</para> + <figure> + <title>Faceted Project Wizard: First Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/webtools/webtools_2.png"/> + </imageobject> + </mediaobject> + </figure> + <para> The first page of most WTP projects allows you to target a specific runtime, + representing a server's library location. It will also provide you the ability to add + this project to an EAR project, and select a pre-selected default set of facets, called + a configuration, rather than manually select each facet you might want.</para> + <para> Selecting the runtime, again, allows the project to install the proper classpaths to + the project so it knows what code to compile against.</para> + <figure> + <title>Faceted Project Wizard: Second Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/webtools/webtools_3.png"/> + </imageobject> + </mediaobject> + </figure> + <para> The second page of the wizard allows you to enable or disable specific facets, as + described above. Some facets may require others, and some may conflict with others, but + on the whole this page allows you to add any number of facets that don't conflict with + each other. </para> + <para> Further pages are specific to either the project type, or the facets selected.</para> + </section> +</chapter>