Author: vpakan(a)redhat.com Date: 2011-02-04 03:02:41 -0500 (Fri, 04 Feb 2011) New Revision: 28999 Modified: trunk/as/docs/reference/en-US/modules.xml trunk/as/docs/reference/en-US/perspective.xml trunk/as/docs/reference/en-US/quick_start.xml trunk/as/docs/reference/en-US/runtimes_servers.xml trunk/as/docs/reference/en-US/webtools.xml Log: Fix typos Modified: trunk/as/docs/reference/en-US/modules.xml =================================================================== --- trunk/as/docs/reference/en-US/modules.xml 2011-02-04 05:13:24 UTC (rev 28998) +++ trunk/as/docs/reference/en-US/modules.xml 2011-02-04 08:02:41 UTC (rev 28999) @@ -4,7 +4,7 @@ <para>In this chapter it will be described how to deploy modules onto the server.</para> <para> - First of all it is necessary to say that deploying to a server is mostly painless. There are several ways to do it provided by WTP, and some additional methods provided by JBoss Tools. These methods are described further in this chapter. + First of all it is necessary to say that deploying to a server is mostly painless. There are several ways to do it provided by WTP and some additional methods provided by JBoss Tools. These methods are described further in this chapter. </para> <section> @@ -37,7 +37,7 @@ This page of the wizard also allows to undeploy modules from the server. For that choose proper module(s) from the right and click the <guibutton> &lt; Remove</guibutton>. The modules will be completely undeployed after restarting your server or republishing. </para> <para> - Generally, for the JBoss AS Server Adapters, publishing using this method will force a default, best-guess, packaging configuration for your project. This best-guess does not publish incrementally, but instead repackages your entire project into a <filename>.war</filename>, <filename>.jar</filename>, or <filename>.ear</filename> as appropriate, and then copies that file into the proper deploy directory. For quicker smarter deployment, you will need to create archives using the Project Archives view (see <xref linkend="Project_archivesView"/>) and customize packaging yourself. + Generally, for the JBoss AS Server Adapters, publishing using this method will force a default, best-guess, packaging configuration for your project. This best-guess does not publish incrementally, but instead repackages your entire project into a <filename>.war</filename>, <filename>.jar</filename>, or <filename>.ear</filename> as appropriate and then copies that file into the proper deploy directory. For quicker smarter deployment, you will need to create archives using the Project Archives view (see <xref linkend="Project_archivesView"/>) and customize packaging yourself. </para> Modified: trunk/as/docs/reference/en-US/perspective.xml =================================================================== --- trunk/as/docs/reference/en-US/perspective.xml 2011-02-04 05:13:24 UTC (rev 28998) +++ trunk/as/docs/reference/en-US/perspective.xml 2011-02-04 08:02:41 UTC (rev 28999) @@ -220,7 +220,7 @@ <para>Stop</para> </entry> <entry> - <para>this will stop the server</para> + <para>This will stop the server</para> </entry> </row> @@ -249,7 +249,7 @@ <para>Add and Remove Projects</para> </entry> <entry> - <para>This option will publish a new project to the server (if its type is supported)</para> + <para>This option will publish a new project to the server (if it&apos;s type is supported)</para> </entry> </row> @@ -279,7 +279,7 @@ Under the server element in the <guilabel>Servers</guilabel> view, you can see modules that are currently deployed to the server and some server extensions that provide additional information on the server. </para> - <para>The context menu for any module allows you to remove it from the server, and force a full or incremental republish upon it.</para> + <para>The context menu for any module allows you to remove it from the server and force a full or incremental republish upon it.</para> <figure> <title>Modules Action</title> @@ -379,7 +379,7 @@ </mediaobject> </figure> <para> - On this preference page you can add a fileset to any server type or to all servers at once. To do this you should select the server type in the combo box and click the <guibutton>Add fileset...</guibutton> button. In the opened <guilabel>New File Filter wizard</guilabel> follow the steps described in <xref linkend="filefilterWiz"/>, and finally click the <guibutton>Apply</guibutton> button on the preference page. + On this preference page you can add a fileset to any server type or to all servers at once. To do this you should select the server type in the combo box and click the <guibutton>Add fileset...</guibutton> button. In the opened <guilabel>New File Filter wizard</guilabel> follow the steps described in <xref linkend="filefilterWiz"/> and finally click the <guibutton>Apply</guibutton> button on the preference page. </para> <para>The defined file filter will be automatically added to new servers during their creation.</para> @@ -400,7 +400,7 @@ </note> <para> - The <guilabel>XML Configuration</guilabel> category itself contains only a list of categories. <guilabel>Ports</guilabel> are provided by default, and display many of the most commonly used ports in the <productname>JBoss Server</productname>. + The <guilabel>XML Configuration</guilabel> category itself contains only a list of categories. <guilabel>Ports</guilabel> are provided by default and display many of the most commonly used ports in the <productname>JBoss Server</productname>. </para> <figure> @@ -555,7 +555,7 @@ </para> <para> - The <guilabel>Server Log</guilabel> view shows relevant information to your server&apos;s startup, shutdown, and publish processes. This allows you to keep an eye on what&apos;s going on (such as automatic incremental deployment if you have it enabled). + The <guilabel>Server Log</guilabel> view shows relevant information to your server&apos;s startup, shutdown and publish processes. This allows you to keep an eye on what&apos;s going on (such as automatic incremental deployment if you have it enabled). </para> <figure> @@ -710,7 +710,7 @@ </figure> - <para>The first tab shows the Jboss server arguments</para> + <para>The first tab shows the JBoss server arguments</para> <para> See the <ulink url="http://docs.jboss.org/jbossas/guides/installguide/r1/en/html/st... Installation Guide </ulink> to find the parameters that can be specified for <productname>JBoss Server</productname>. </para> @@ -729,7 +729,7 @@ </note> <para> - On the second tab you find the main class used for launching JBoss AS (the default is <code>org.jboss.Main</code>). this value can be changed if necessary. + On the second tab you find the main class used for launching JBoss AS (the default is <code>org.jboss.Main</code>). This value can be changed if necessary. </para> <para> @@ -855,11 +855,11 @@ </note> <para> - <filename>JAR</filename> is the standard archive type, and does very little configuration, leaving most of the work up to you. You can customize the name, add folders, filesets, and inner JARs to it. + <filename>JAR</filename> is the standard archive type and does very little configuration, leaving most of the work up to you. You can customize the name, add folders, filesets and inner JARs to it. </para> <para> - The other types, for the most part, simply start off with a default setting, usually the JAR with some specific children based on an expected structure of the project. For example, if the project is a Dynamic Web Project, and you create a <filename>WAR</filename> archive, the archive will be created with a few filesets relevant to the known structure of the project. + The other types, for the most part, simply start off with a default setting, usually the JAR with some specific children based on an expected structure of the project. For example, if the project is a Dynamic Web Project and you create a <filename>WAR</filename> archive, the archive will be created with a few filesets relevant to the known structure of the project. </para> <para> @@ -936,10 +936,10 @@ <section id="CreatingaFileSet"> <title>Creating a FileSet</title> <para> - To create a new fileset, right click on an available target location such as an archive, a nested archive, or a folder within an archive, and select the <guimenuitem>New Fileset</guimenuitem> option. + To create a new fileset, right click on an available target location such as an archive, a nested archive, or a folder within an archive and select the <guimenuitem>New Fileset</guimenuitem> option. </para> <para> - The <guilabel>New Fileset</guilabel> wizard requires a destination (where the files will be located), and a root directory (or where the files are coming from). The source can be anywhere in the workspace or from the filesystem at large. + The <guilabel>New Fileset</guilabel> wizard requires a destination (where the files will be located) and a root directory (or where the files are coming from). The source can be anywhere in the workspace or from the filesystem at large. </para> <figure> @@ -1043,7 +1043,7 @@ </entry> <entry> - <para>This action is enabled only on top-level archives, and initiates a full build on that archive</para> + <para>This action is enabled only on top-level archives and initiates a full build on that archive</para> </entry> </row> Modified: trunk/as/docs/reference/en-US/quick_start.xml =================================================================== --- trunk/as/docs/reference/en-US/quick_start.xml 2011-02-04 05:13:24 UTC (rev 28998) +++ trunk/as/docs/reference/en-US/quick_start.xml 2011-02-04 08:02:41 UTC (rev 28999) @@ -31,11 +31,11 @@ </entry> <entry> <para> - Using WTP, the JBoss AS plugin allows you to work with the server in run or debug mode. You can easily install runtimes and servers, copy the existing runtime configuration or configure it up to your needs. + Using WTP the JBoss AS plugin allows you to work with the server in run or debug mode. You can easily install runtimes and servers, copy the existing runtime configuration or configure it up to your needs. </para> </entry> <entry> - <link linkend="runtimes_servers">runtimes and servers</link> + <link linkend="runtimes_servers">Runtimes and servers</link> </entry> </row> @@ -45,7 +45,7 @@ </entry> <entry> <para> - It allows for easy management of an installed JBoss Server and includes the standard Console and Properties views, and the specially added Project archives and Servers views. + It provides easy management of an installed JBoss Server and includes the standard Console and Properties views and the specially added Project archives and Servers views. </para> </entry> <entry> @@ -61,7 +61,7 @@ <para>Provides a number of ways, using WTP and JBoss Tools, to deploy either a project or a single file on the server.</para> </entry> <entry> - <link linkend="modules">deploying modules</link> + <link linkend="modules">Deploying modules</link> </entry> </row> @@ -95,7 +95,7 @@ <title>Starting JBoss Server</title> <para> - Starting <productname>JBoss Server</productname> is quite simple. You can control the server behavior with the help of a special toolbar in the <guilabel>Servers</guilabel> view where you can <guibutton>start</guibutton> it in a regular or debug mode, <guibutton>stop</guibutton> or <guibutton>restart</guibutton> it, and <guibutton>publish</guibutton> to the server. + Starting <productname>JBoss Server</productname> is quite simple. You can control the server behavior with the help of a special toolbar in the <guilabel>Servers</guilabel> view where you can <guibutton>start</guibutton> it in a regular or debug mode, <guibutton>stop</guibutton> or <guibutton>restart</guibutton> it and <guibutton>publish</guibutton> to the server. </para> <figure> Modified: trunk/as/docs/reference/en-US/runtimes_servers.xml =================================================================== --- trunk/as/docs/reference/en-US/runtimes_servers.xml 2011-02-04 05:13:24 UTC (rev 28998) +++ trunk/as/docs/reference/en-US/runtimes_servers.xml 2011-02-04 08:02:41 UTC (rev 28999) @@ -18,7 +18,7 @@ First of all it is necessary to mention that the JBoss AS plugin makes use of WTP. This includes starting and stopping servers in run or debug mode. It also includes targeting WTP projects, such as Dynamic Web Projects, to certain server runtimes in order to ensure that the proper JARs from a specific server are added to the project's classpath properly. </para> <para> - In order to get started creating, running, and debugging J2EE applications, we should create our <property>runtime</property> and <property>server</property> instances. + In order to get started creating, running and debugging J2EE applications, we should create our <property>runtime</property> and <property>server</property> instances. </para> <section> @@ -32,7 +32,7 @@ </listitem> <listitem> <para> - For <property>JBoss server</property> at least, it provides the necessary information to allow the server to be started and stopped, and provides information on which JARs to run and which configuration to use. + For <property>JBoss server</property> at least, it provides the necessary information to allow the server to be started and stopped and provides information on which JARs to run and which configuration to use. </para> </listitem> </itemizedlist> @@ -41,7 +41,7 @@ <para> You can install runtimes into Eclipse by selecting <menuchoice><guimenuitem>Window</guimenuitem> <guimenuitem>Preferences</guimenuitem> - </menuchoice> menu, and then selecting <menuchoice><guimenuitem>Server</guimenuitem> + </menuchoice> menu and then selecting <menuchoice><guimenuitem>Server</guimenuitem> <guimenuitem>Runtime Environments</guimenuitem> </menuchoice> from the categories available on the left. </para> @@ -88,7 +88,7 @@ </note> <para> - You will also note a Deploy-Only Runtime type. This type does not provide a classpath for WTP projects. It is used solely by its server type for the purpose of setting up a deploy directory for users who do not wish to make use of starting, stopping, or debugging their projects inside Eclipse. + You will also note a Deploy-Only Runtime type. This type does not provide a classpath for WTP projects. It is used solely by it&apos;s server type for the purpose of setting up a deploy directory for users who do not wish to make use of starting, stopping, or debugging their projects inside Eclipse. </para> <figure id="add_runtime_figure"> @@ -100,7 +100,7 @@ </mediaobject> </figure> - <para>The following table describes all the available options of the currant wizard page.</para> + <para>The following table describes all the available options of the current wizard page.</para> <table> <title>Server Runtime Wizard Parameters</title> <tgroup cols="2"> @@ -173,14 +173,14 @@ </table> <para> - As a result of having each runtime represent a specific configuration rather than the server installation as a whole, it is very likely you will create several different runtimes to test each of your configurations. So it becomes important to ensure your runtimes, and later your servers, are given descriptive names that help you to remember which is which. + As a result of having each runtime represent a specific configuration rather than the server installation as a whole, it is very likely you will create several different runtimes to test each of your configurations. So it becomes important to ensure your runtimes and later your servers, are given descriptive names that help you to remember which is which. </para> <para>Click the <guibutton>Finish</guibutton> button to see your new runtime in the list.</para> <note> <title>Note:</title> <para> - If you edit the configuration of a runtime, the changes don't affect the settings of the servers that currently use the runtime. To apply the changes to them also, you should double right click the server, select <menuchoice><guimenuitem>Overview</guimenuitem> + If you edit the configuration of a runtime, the changes don't affect the settings of the servers that currently use the runtime. To apply the changes to them also, you should double left click on the server, select <menuchoice><guimenuitem>Overview</guimenuitem> <guimenuitem>Runtime Environment</guimenuitem> </menuchoice>, make sure that necessary configuration is chosen, click the <guibutton>Finish</guibutton> button and then <guibutton>Save</guibutton> button. </para> @@ -271,7 +271,7 @@ </mediaobject> </figure> <para> - Change the name, click the <guibutton>Browse</guibutton> button, and select your configuration location or leave as it is if you want it to be located together with other runtime configurations. + Change the name, click the <guibutton>Browse</guibutton> button and select your configuration location or leave as it is if you want it to be located together with other runtime configurations. </para> <figure> <title>Copy the existing configuration</title> @@ -301,7 +301,7 @@ <section> <title>Servers</title> <para> - WTP servers are Eclipse-representations of a back end server installation. They are used to start or stop servers, deploy to servers, or debug code that will run on the server. They keep track of the modules (JARs, WARs, etc) you deploy to the server, and also allow you to undeploy those modules (see <xref linkend="run_on_server_wizard"/>). + WTP servers are Eclipse-representations of a back end server installation. They are used to start or stop servers, deploy to servers, or debug code that will run on the server. They keep track of the modules (JARs, WARs, etc) you deploy to the server and also allow you to undeploy those modules (see <xref linkend="run_on_server_wizard"/>). </para> <para> Servers can be started or stopped with different <link linkend="com_line_arg">command-line arguments</link>. They are often backed by a runtime object representing that server's location. @@ -322,14 +322,14 @@ </mediaobject> </figure> <para> - A server object keeps track of things like command line arguments when starting or stopping, and the runtimes keep track of the location of the installation. Thus, each server instance must be backed by an appropriate runtime. + A server object keeps track of things like command line arguments when starting or stopping and the runtimes keep track of the location of the installation. Thus, each server instance must be backed by an appropriate runtime. </para> <para> The <guilabel>New server wizard</guilabel> allows you to name the server via the <guilabel>Server name</guilabel> field, or you can use a generated default name .If it is necessary to restore the default name, click the <guibutton>Reset default</guibutton> button (<inlinemediaobject> <imageobject><imagedata fileref="images/runtimes_servers/runtimes_servers_4d.png"/></imageobject></inlinemediaobject>). </para> <para> - You can select the appropriate runtime you from the <guilabel>Server runtime environment</guilabel> combobox. If there is no runtime that matches your needs just press the <guilabel>Add...</guilabel> link nearby to bring up the wizard for creating a new runtime (see <xref linkend="add_runtime_figure"/>). To configure an existing runtimes you should go to server preferences by pressing the <guilabel>Configure runtime environments...</guilabel> link. + You can select the appropriate runtime from the <guilabel>Server runtime environment</guilabel> combo box. If there is no runtime that matches your needs just press the <guilabel>Add...</guilabel> link nearby to bring up the wizard for creating a new runtime (see <xref linkend="add_runtime_figure"/>). To configure an existing runtimes you should go to server preferences by pressing the <guilabel>Configure runtime environments...</guilabel> link. </para> <para>If the server you want to create does not have any installed runtime yet, the combo box and the links are absent.</para> @@ -344,7 +344,7 @@ </figure> <para> - In this case the next page of the wizard which has the same form as in <link linkend="add_runtime_figure">the previous section</link>, and will ask you to create the associated runtime. + In this case the next page of the wizard which has the same form as in <link linkend="add_runtime_figure">the previous section</link> and will ask you to create the associated runtime. </para> <para> Either way, after targeting your server to a runtime, the final screen in this wizard presents a summary of the selected options, giving you a chance to verify that you have selected the appropriate runtime. Modified: trunk/as/docs/reference/en-US/webtools.xml =================================================================== --- trunk/as/docs/reference/en-US/webtools.xml 2011-02-04 05:13:24 UTC (rev 28998) +++ trunk/as/docs/reference/en-US/webtools.xml 2011-02-04 08:02:41 UTC (rev 28999) @@ -2,7 +2,7 @@ <chapter id="webtools"> <title>Projects</title> <para> - The most popular of the projects we deal with are the J2EE ones, such as Dynamic Web Project, EJB Project, or EAR project. <productname>JBoss Tools</productname> web projects include Struts, JSF and Seam projects. These are referred to as faceted projects. This chapter will cover facets, which are used to provide provide a consistent structure and packaging features to any type of project. + The most popular of the projects we deal with are the J2EE ones, such as Dynamic Web Project, EJB Project, or EAR project. <productname>JBoss Tools</productname> web projects include Struts, JSF and Seam projects. These are referred to as faceted projects. This chapter will cover facets, which are used to provide a consistent structure and packaging features to any type of project. </para> <section> @@ -16,7 +16,7 @@ </para> <para> - However, the benefit of this is that the structure of your projects is then known, and packaging it up <emphasis>should</emphasis> be trivial. 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 (see <xref linkend="Project_archivesView"/>). + However, the benefit of this is that the structure of your projects is then known and packaging it up <emphasis>should</emphasis> be trivial. 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 (see <xref linkend="Project_archivesView"/>). </para> </section> @@ -42,7 +42,7 @@ <para>Click the <guibutton>Next</guibutton> button and you will see a Dynamic Web Project page like on the figure below.</para> <para> - The first page of most WTP projects allows you to target a specific runtime, which represents a server's library location. It will also provide you the ability to add this project to an EAR project, and select a preselected default set of facets, called a configuration, rather than manually select each required facet. + The first page of most WTP projects allows you to target a specific runtime, which represents a server's library location. It will also provide you the ability to add this project to an EAR project and select a preselected default set of facets, called a configuration, rather than manually select each required facet. </para> <para> Selecting the runtime allows the project to install the proper classpaths to the project so it knows what code to compile against.