Author: smukhina Date: 2007-12-03 10:07:16 -0500 (Mon, 03 Dec 2007) New Revision: 5197 Modified: trunk/as/docs/reference/en/modules/modules.xml trunk/as/docs/reference/en/modules/perspective.xml trunk/as/docs/reference/en/modules/runtimes_servers.xml trunk/as/docs/reference/en/modules/webtools.xml Log: http://jira.jboss.com/jira/browse/RHDS-279 Modified: trunk/as/docs/reference/en/modules/modules.xml =================================================================== --- trunk/as/docs/reference/en/modules/modules.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/modules.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -2,17 +2,17 @@ <chapter id="modules"> <title>Deploying Modules</title> -<para>In this chapter it will be described how to deploy modules onto the server</para> +<para>In this chapter it will be described how to deploy modules onto the server.</para> <para> - Deploying to a server is mostly painless. - There are several ways to do it provided by Webtools, - and some additional methods provided by JBoss Tools. </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 discribed further in this chapter</para> <section><title>WTP Projects</title> <section><title>Run On Server</title> <para> - The first WTP method is to right-click on a webtools project, + The first WTP method is to right-click on a WTP project, such as a dynamic web project, ejb project, or ear project - and then selecting <emphasis><property>Run As &gt; Run on Server</property></emphasis>. + and then select <emphasis><property>Run As &gt; Run on Server</property></emphasis>. The resulting dialog allows you to select which supporting server the project can be published to. </para> <figure> @@ -23,7 +23,7 @@ </imageobject> </mediaobject> </figure> - <para>Click <emphasis><property>Next</property></emphasis> button to see add or remove projects page where you can choose propjects to configure them on server.</para> + <para>Click <emphasis><property>Next</property></emphasis> button to see add or remove projects page where you can choose projects to configure them on server.</para> <figure> <title>Add or Remove Projects</title> <mediaobject> @@ -60,7 +60,7 @@ </figure> <para> - If the selected module is a webtools project, + If the selected module is a WTP project, it will be published as in the <emphasis><property>Run on Server</property></emphasis> option, with a best-guess full package. If, however, the selected element is an archive from the <emphasis>Project Archives View</emphasis>, Modified: trunk/as/docs/reference/en/modules/perspective.xml =================================================================== --- trunk/as/docs/reference/en/modules/perspective.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/perspective.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -203,12 +203,12 @@ <section id="Project_archivesView"> <title>Project archives View</title> <para>Every application, whether plain old Java, J2EE, or some other language altogether, needs to be packaged in some way. In Java-related projects, - many people use ANT. JBoss Developer Studio comes with our own archives tool with a bit easier and less-verbose XML and a handy user interface.</para> + many people use ANT. JBoss Tools comes with our own archives tool with a bit easier and less-verbose XML and a handy user interface.</para> <para>The Project Archives plugin consists primarily of a view to set up each packaging configuration. Each project can enable or disable its builder, or depend on the global setting.</para> <para>The packaging configuration for each project is stored in that project's root folder, and is in a file named <property>.packages</property>, which has a fairly simple XML structure. Modifying the file by hand is neither required nor recommended, and using the UI is the official way of modifying your packaging structure.</para> <para>Aside from the builder, the other preferences for the plugin are mostly cosmetic, allowing you to show full or truncated paths, show the project at the - root, etc. None of these have any effect on the functionality of the packaging plugin.</para> + root, etc. None of these has any effect on the functionality of the packaging plugin.</para> <section id="Creating an archive"> <title>Creating an Archive</title> Modified: trunk/as/docs/reference/en/modules/runtimes_servers.xml =================================================================== --- trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -18,18 +18,18 @@ <!-- The Eclipse Web Tools Platform (WTP) project extends the Eclipse platform with tools for developing Web and Java EE applications. It includes source and graphical editors for a variety of languages, wizards and built-in applications to simplify development, and tools and APIs to support deploying, running, and testing apps. --> - <para>The JBoss AS plugin makes use of Webtools. This includes starting and stopping servers in run or debug mode. It also includes - targeting webtools projects, such as dynamic web projects, to certain server runtimes in order to ensure that the proper jars + <para>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 must start with creating our <property>runtime</property> and <property>server</property> instances.</para> <section> - <title>Webtools Runtimes</title> + <title>WTP Runtimes</title> <para>In JBoss Tools, the main purpose of Server Runtimes is to point to a server installation somewhere on disk. In our case, this will be a JBoss installation, and it can than be used for two primary purposes:</para> <itemizedlist> - <listitem><para>it provides classpath additions to webtools projects that require them.</para></listitem> + <listitem><para>it provides classpath additions to WTP projects that require them.</para></listitem> <listitem><para>For JBoss server at least, it provides information necessary for the starting and stopping of the server, it tells which jars to run and which configuration to use.</para></listitem> </itemizedlist> @@ -47,7 +47,7 @@ <para>From this preference page you can see what runtimes are declared, and what type they are. In the image shown above, there are two declared runtimes, including a JBoss 4.2 instance.</para> <para>To create a JBoss runtime, we begin by clicking the <emphasis><property>Add</property></emphasis> button. This will open another dialog that allows us to choose what type - of runtime we want to create. Most of the runtime options are provided by webtools, but those provided by JBoss Tools are the ones we will focus on.</para> + of runtime we want to create. Most of the runtime options are provided by WTP, but those provided by JBoss Tools are the ones we will focus on.</para> <figure> <title>Adding a Runtime</title> <mediaobject> @@ -56,9 +56,9 @@ </imageobject> </mediaobject> </figure> - <para>As seen above, there appear to be two JBoss categories. The first is contributed by webtools, and is a generic adapter that is not upkept very well. - For this reason, JBoss Tools provides updated and supported adapters of our own. There is one for each of JBoss 3.2, 4.0, amd 4.2. You'll also note a deploy-only - runtime type. This type provides no classpath for webtools projects. It is used solely by it's server type for the purpose of setting up a deploy directory + <para>As seen above, there appear to be two JBoss categories. The first is contributed by WTP, and is a generic adapter that is not upkept very well. + For this reason, JBoss Tools provides updated and supported adapters of our own. There is one for each of JBoss 3.2, 4.0, and 4.2. You'll also note a deploy-only + runtime type. This type provides no classpath for WTP projects. It is used solely by it's server type for the purpose of setting up a deploy directory for users who don't wish to make use of starting, stopping, or debugging their projects inside eclipse.</para> <figure> <title>Adding a JBoss 4.2 Runtime</title> @@ -81,14 +81,14 @@ <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'll create several different runtimes to test each of your configurations. It becomes important to ensure your runtimes, and later your servers, are given descriptive names that help you remember which is which. It will do no good to try to remember if "JBoss-runtime 5" is the 4.0 install with ejb3? Or the 4.2 install's custom configuration you decided to create.</para> - <para>After pressing finish, you'll see that your new runtime has been added to the list and can now be targeted by webtools type projects or servers, both of which we'll get to later.</para> + <para>After pressing finish, you'll see that your new runtime has been added to the list and can now be targeted by WTP type projects or servers, both of which we'll get to later.</para> </section> </section> <section> - <title>Webtools Servers</title> - <para>Webtools servers are eclipse-representations of a backing 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 what modules (jars, wars, etc) + <title>WTP Servers</title> + <para>WTP servers are eclipse-representations of a backing 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 what modules (jars, wars, etc) you deploy to the server and also allow you to undeploy those modules. </para> <para>Servers can be started or stopped with different command-line arguments. They are often backed by a runtime object representing that server's location.</para> <section> Modified: trunk/as/docs/reference/en/modules/webtools.xml =================================================================== --- trunk/as/docs/reference/en/modules/webtools.xml 2007-12-03 15:01:26 UTC (rev 5196) +++ trunk/as/docs/reference/en/modules/webtools.xml 2007-12-03 15:07:16 UTC (rev 5197) @@ -1,14 +1,14 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="webtools"> - <title>Webtools Projects</title> + <title>WTP Projects</title> <para>This chapter covers how to select installed runtime/server in your web project</para> <section><title>Description</title> <para> - Webtools provides what are called "faceted" projects. + 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> + 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