4:38 p.m.
Author: smukhina
Date: 2007-11-29 10:38:08 -0500 (Thu, 29 Nov 2007)
New Revision: 5151
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/resources/styles/en/html.css
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-11-29 14:54:23 UTC (rev 5150)
+++ trunk/as/docs/reference/en/modules/modules.xml 2007-11-29 15:38:08 UTC (rev 5151)
@@ -5,7 +5,7 @@
<para>
Deploying to a server is mostly painless.
There are several ways to do it provided by Webtools,
- and some additional methods provided by JBDS. </para>
+ and some additional methods provided by JBoss Tools. </para>
<section><title>WTP Projects</title>
<section><title>Run On Server</title>
<para>
@@ -37,7 +37,7 @@
for your project. This best-guess does <emphasis>not</emphasis>
publish incrementally, but instead repackages your entire
project into a .war, .jar, or .ear as appropriate, and
- then coppies that file into the proper deploy directory.
+ then copies that file into the proper deploy directory.
For quicker smarter deployment, you will need to create
archives using the <emphasis>Project Archives</emphasis>
view and customize packaging yourself.</para>
Modified: trunk/as/docs/reference/en/modules/perspective.xml
===================================================================
--- trunk/as/docs/reference/en/modules/perspective.xml 2007-11-29 14:54:23 UTC (rev 5150)
+++ trunk/as/docs/reference/en/modules/perspective.xml 2007-11-29 15:38:08 UTC (rev 5151)
@@ -42,7 +42,7 @@
</imageobject>
</mediaobject>
</figure>
- <para>Extender is meant to provide additional functionality relevent to the
server selected in the top half of the view. If a standard server element is selected from
above, some
+ <para>Extender is meant to provide additional functionality relevant to the
server selected in the top half of the view. If a standard server element is selected from
above, some
of the extensions may still provide the additional information. Others may not.
So, let's look at the currently available extensions to the JBoss
Server's View.</para>
@@ -65,7 +65,7 @@
</imageobject>
</mediaobject>
</figure>
- <para>The <property>Event Log</property> will show relevent
information to your server's startup, shutdown, and publish processes. This allows
+ <para>The <property>Event Log</property> will show relevant
information to your server's startup, shutdown, and publish processes. This allows
you to keep an eye on what's going on (such as automatic incremental
deployment if you have it enabled).
The only action available is to clear the event log. However if the properties
view is opened, you can receive further
information on each event log item (when available).</para>
@@ -160,8 +160,8 @@
</mediaobject>
</figure>
<para>The Server section of the view lists all declared servers and their
current states, that is, whether they are started or stopped. By Double-clicking on each
server, an editor window will appear allowing you to edit parts of that server.
- The editor will also link you to modify that server's launch configuration, set
command line arguments, and other things that are relevent to launching the
server.</para>
- <para>A username/password is available in the UI when configuring the server.
If you get an SecurityException when trying to launch the server it is most likely because
your server is protected and hence you need to fill the username/password fields with
apropriate values.</para>
+ The editor will also link you to modify that server's launch configuration, set
command line arguments, and other things that are relevant to launching the
server.</para>
+ <para>A username/password is available in the UI when configuring the server.
If you get an SecurityException when trying to launch the server it is most likely because
your server is protected and hence you need to fill the username/password fields with
appropriate values.</para>
<figure>
<title></title>
<mediaobject>
@@ -204,7 +204,7 @@
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>
<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
reccommended, and using the UI is the official way of modifying your packaging
structure.</para>
+ 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>
Modified: trunk/as/docs/reference/en/modules/runtimes_servers.xml
===================================================================
--- trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-11-29 14:54:23 UTC (rev
5150)
+++ trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-11-29 15:38:08 UTC (rev
5151)
@@ -20,15 +20,16 @@
<section>
<title>Webtools Runtimes</title>
- <para>In JBDS, Server Runtimes have one main purpose: 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.
- First, it provides classpath additions to webtools projects that require them.
Second, for JBoss server at least, it provides information necessary
- for the starting and stopping of the server, such as which jars to run and which
configuration to use. </para>
-
-
+ <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>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>
+
<section><title>Installing a new Runtime</title>
<para>You can install runtimes into eclipse from the
<emphasis><property>Window > Preferences...
</property></emphasis>
- menu, and then selecting <emphasis><property>Server >
Installed Runtimes</property></emphasis> from the categories
available.</para>
+ menu, and then select <emphasis><property>Server > Installed
Runtimes</property></emphasis> from the categories available.</para>
<figure>
<title>Installed Runtimes</title>
<mediaobject>
@@ -40,7 +41,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 JBDS are the ones we will focus on.</para>
+ 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>
<figure>
<title>Adding a Runtime</title>
<mediaobject>
@@ -50,7 +51,7 @@
</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, JBDS 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
+ 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
for users who don't wish to make use of starting, stopping, or debugging
their projects inside eclipse.</para>
<figure>
Modified: trunk/as/docs/resources/styles/en/html.css
===================================================================
--- trunk/as/docs/resources/styles/en/html.css 2007-11-29 14:54:23 UTC (rev 5150)
+++ trunk/as/docs/resources/styles/en/html.css 2007-11-29 15:38:08 UTC (rev 5151)
@@ -99,7 +99,7 @@
div.book div.mediaobject{
-text-align:center;
+text-align:left;
}
div.mediaobject, div.mediaobject img *{