Author: afedosik Date: 2007-12-27 09:41:20 -0500 (Thu, 27 Dec 2007) New Revision: 5459 Modified: trunk/as/docs/reference/en/images/perspective/perspective_3.png trunk/as/docs/reference/en/images/runtimes_servers/runtimes_servers_2.png trunk/as/docs/reference/en/modules/perspective.xml trunk/as/docs/reference/en/modules/runtimes_servers.xml Log: http://jira.jboss.com/jira/browse/JBDS-199 guide update according to remarks Modified: trunk/as/docs/reference/en/images/perspective/perspective_3.png =================================================================== (Binary files differ) Modified: trunk/as/docs/reference/en/images/runtimes_servers/runtimes_servers_2.png =================================================================== (Binary files differ) Modified: trunk/as/docs/reference/en/modules/perspective.xml =================================================================== --- trunk/as/docs/reference/en/modules/perspective.xml 2007-12-27 12:50:12 UTC (rev 5458) +++ trunk/as/docs/reference/en/modules/perspective.xml 2007-12-27 14:41:20 UTC (rev 5459) @@ -268,10 +268,60 @@ </imageobject> </mediaobject> </figure> - <para>The context menu on the items in the view is extendable, but there are several that come standard. The first is the <property>Build Archive</property> action, enabled - only on top-level archives, which initiates a full build on that archive. Editing and deleting nodes are also standard actions, with deletion not needing - an explanation. The edit action brings up the wizard associated with that particular node type and allows the details to be changed. The final action - contribution here is the ability to publish to a declared server.</para> + <para>The context menu on the items in the view is extendable, but there are several that come standard.</para> + + <table> + <title>Context Menu on the Item</title> + <tgroup cols="2"> + <colspec colnum="1" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + + + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> + + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + + <tbody> + + <row> + <entry><para>Build Archive (Full)</para></entry> + + <entry><para>The action enabled only on top-level archives, which initiates a full build on that archive</para></entry> + </row> + + <row> + <entry><para>Edit Archive</para></entry> + + <entry><para>Standard action that brings up the wizard associated with that particular node type and allows the details to be changed</para></entry> + </row> + + <row> + <entry><para>Delete Archive</para></entry> + + <entry><para>Deleting node is standard action with deletion not needing an explanation</para></entry> + </row> + + <row> + <entry><para>Publish To Server</para></entry> + + <entry><para>The action means the ability to publish to a declared server</para></entry> + </row> + + </tbody> + </tgroup> + </table> + + + + </section> <section id="PublishToServer"> <title>Publish to Server</title> Modified: trunk/as/docs/reference/en/modules/runtimes_servers.xml =================================================================== --- trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-27 12:50:12 UTC (rev 5458) +++ trunk/as/docs/reference/en/modules/runtimes_servers.xml 2007-12-27 14:41:20 UTC (rev 5459) @@ -33,7 +33,7 @@ <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> + <section id="InstNewRuntime"><title>Installing a new Runtime</title> <para>You can install runtimes into eclipse from the <emphasis><property>Window &gt; Preferences... </property></emphasis> menu, and then select <emphasis><property>Server &gt; Installed Runtimes</property></emphasis> from the categories available.</para> <figure> @@ -88,7 +88,7 @@ <section> <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) + <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 the 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> @@ -108,8 +108,7 @@ <para>Because there may be many runtimes of each type declared, the wizard allows you to select which runtime you want your server to be backed by. The combo box below the view lets you select which declared runtime to use. For example, if there were already multiple JBoss 4.2 runtimes declared, the combo box would list all of the 4.2 runtimes available. </para> <para>If none of the runtimes declared are one you want to use, for example if you declared a default and a minimal runtime before but now want your server - to be backed by the ALL configuration, then you can click on the <emphasis><property>Installed Runtimes... </property></emphasis> button to bring up the preference page - shown at the beginning of this chapter. </para> + to be backed by the ALL configuration, then you can click on the <emphasis><property>Installed Runtimes... </property></emphasis> button to bring up the preference page shown at the beginning of this chapter.</para> <figure> <title>Installed Server Runtime Environments</title> <mediaobject>