Author: ochikvina
Date: 2008-01-21 12:00:58 -0500 (Mon, 21 Jan 2008)
New Revision: 5842
Modified:
trunk/as/docs/reference/en/modules/perspective.xml
Log:
http://jira.jboss.com/jira/browse/JBDS-199 - rearrangment a bit data according to the
task
Modified: trunk/as/docs/reference/en/modules/perspective.xml
===================================================================
--- trunk/as/docs/reference/en/modules/perspective.xml 2008-01-21 16:57:29 UTC (rev 5841)
+++ trunk/as/docs/reference/en/modules/perspective.xml 2008-01-21 17:00:58 UTC (rev 5842)
@@ -25,12 +25,11 @@
<?dbhtml filename="JBossServerView.html"?>
<title>The JBoss Servers View</title>
<para>This chapter will focus on the the JBoss Server's View.
</para>
- <para>The JBoss Servers View is
- based on the WTP view, Servers View. The top half of the JBoss Servers View
essentially
- embeds the original Servers View directly into it, making slight changes to
the context
- menu. A second half was added to provide additional information about the
server
- selected in the top half. In the image provided, categories in the second
half include
- which modules are currently deployed.</para>
+ <para>The JBoss Servers View is based on the WTP view, Servers View. The
top half of the
+ JBoss Servers View essentially embeds the original Servers View directly into
it, making
+ slight changes to the context menu. A second half was added to provide
additional
+ information about the server selected in the top half. In the image provided,
categories
+ in the second half include which modules are currently
deployed.</para>
<figure>
<title>The JBoss Servers View</title>
@@ -175,9 +174,10 @@
</mediaobject>
</figure>
- <para>Also you can see the server's publish status in the JBoss Servers
view that allows you to
- see if changes are awaiting (Republish), are being updated (Publishing...) or are
in-sync
- (Synchronized).</para>
+ <para>Now, let's return to the first part of the JBoss Servers view
where all declared
+ servers are represented as well as their current states, that is, whether they
are started
+ or stopped. It also shows the server's publish status that allows you to see
if changes are
+ awaiting (Republish), are being updated (Publishing...) or are in-sync
(Synchronized).</para>
<figure>
<title>Server's Publish Status</title>
<mediaobject>
@@ -186,22 +186,26 @@
</imageobject>
</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 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>
+
+ <para>By double-clicking on any server in the Server section of the view, 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
+ relevant to launching the server.</para>
+
<figure>
- <title/>
+ <title>Preferences Page for the Chosen Server</title>
<mediaobject>
<imageobject>
<imagedata
fileref="images/perspective/perspective_20.png"/>
</imageobject>
</mediaobject>
</figure>
+
+ <para>At the figure above you can see that 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>
+
<para>The view's toolbar shown below provides quick access to starting a
server (in debug mode,
run mode, or profile mode), restarting the server, stopping the server, or
publishing to the
server.</para>
@@ -213,15 +217,15 @@
</imageobject>
</mediaobject>
</figure>
+
<para>In order to debug your applications or EJB's that are deployed to the
server, you must
start the server in debug mode. By starting the server in debug mode, eclipse
will allow you
to set breakpoints on code in your workspace and step through the
code.</para>
- <para>The publish icon, on the extreme right, will republish any modules where
it has determined
+ <para>The publish icon on the extreme right will republish any modules where it
has determined
the workspace is out of sync with the server. It will attempt to do an
incremental publish
if it turns out that the module in question is capable of doing
one.</para>
- <para>Because the JBoss servers have few properties to edit in the editor, a
shortcut to the
- launch configuration has been provided in the context menu when right-clicking on
a
- server.</para>
+ <para>As the JBoss servers have few properties to edit in the editor, a
shortcut to the
+ launch configuration has been provided in the context menu when right-clicking on
a server.</para>
<figure>
<title>Launch Configuration</title>
<mediaobject>
@@ -231,8 +235,7 @@
</mediaobject>
</figure>
- <para>The following table describes all those additional
- properties.</para>
+ <para>The following table describes all those additional
properties.</para>
<table>
<title>Server Properties through the Context Menu</title>
<tgroup cols="2">
@@ -302,8 +305,8 @@
<para>Publish</para>
</entry>
<entry>
- <para>The action for synching the publish information
- between the server and workspace.</para>
+ <para>The action for synching the publish information
between the server and
+ workspace.</para>
</entry>
</row>
@@ -321,7 +324,8 @@
<para>Twiddle Server</para>
</entry>
<entry>
- <para>The option provides a dialog for running Twiddle
commands against the Twiddle Server.</para>
+ <para>The option provides a dialog for running Twiddle
commands against the
+ Twiddle Server.</para>
</entry>
</row>
@@ -330,7 +334,8 @@
<para>Edit Launch Configuration</para>
</entry>
<entry>
- <para>The option that provides an editor for editing launch
configuration properties of the proper server.</para>
+ <para>The option that provides an editor for editing launch
configuration
+ properties of the proper server.</para>
</entry>
</row>
@@ -339,17 +344,18 @@
<para>Add and Remove Projects</para>
</entry>
<entry>
- <para>The option allows to publish a new project to the
server (if its type is supported).</para>
+ <para>The option allows to publish a new project to the
server (if its type
+ is supported).</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
- <para>Mentioned above Twiddle is a JMX library that comes with JBoss, and you
can use it to access any
- variables that exposed via the JBoss JMX interfaces.</para>
-
+ <para>Mentioned above Twiddle is a JMX library that comes with JBoss, and you
can use it to
+ access any variables that exposed via the JBoss JMX interfaces.</para>
+
<section id="Project_archivesView">
<title>Project archives View</title>
<para>Every application, whether plain old Java, J2EE, or some other
language altogether,
@@ -371,7 +377,7 @@
<title>Creating an Archive</title>
<para>When creating a new archive, you have some different options at
your disposal. If
the project has no <property>.packages</property> file, your
options will be
- presented to you all at once for you to choose from (as above). Otherwise
you will
+ presented to you all at once to choose from (as above). Otherwise you
will
right-click inside the view and select <emphasis>
<property>New Archive</property>
</emphasis> to see your archive type options.</para>
@@ -403,7 +409,7 @@
</mediaobject>
</figure>
- <para>The page is pretty simple. All it asks is for the name of your
new archive, a
+ <para>The page is pretty simple. All it asks for is the name of your
new archive, a
destination, which we'll get to in a moment, and whether the archive
is exploded or
packaged up.</para>
<para>The destination of an archive can be anywhere on the filesystem,
anywhere in the