Author: smukhina Date: 2008-10-29 12:17:50 -0400 (Wed, 29 Oct 2008) New Revision: 11301 Added: branches/jbosstools-3.0.0.Beta1/as/docs/reference/en/master_output.xml branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/en/master_output.xml Modified: branches/jbosstools-3.0.0.Beta1/as/docs/reference/pom.xml branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/pom.xml Log: https://jira.jboss.org/jira/browse/JBDS-463 markers for new and updated are added Added: branches/jbosstools-3.0.0.Beta1/as/docs/reference/en/master_output.xml =================================================================== --- branches/jbosstools-3.0.0.Beta1/as/docs/reference/en/master_output.xml (rev 0) +++ branches/jbosstools-3.0.0.Beta1/as/docs/reference/en/master_output.xml 2008-10-29 16:17:50 UTC (rev 11301) @@ -0,0 +1,1763 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" +"http://www.docbook.org/xml/4.3/docbookx.dtd" + +[<!ENTITY quick_start SYSTEM "modules/quick_start.xml"> +<!ENTITY runtimes_servers SYSTEM "modules/runtimes_servers.xml"> +<!ENTITY perspective SYSTEM "modules/perspective.xml"> +<!ENTITY webtools SYSTEM "modules/webtools.xml"> +<!ENTITY modules SYSTEM "modules/modules.xml"> +<!ENTITY tptp_support SYSTEM "modules/tptp_support.xml"> + +<!ENTITY seamlink "../../seam/html_single/index.html"> +<!ENTITY aslink "../../as/html_single/index.html"> +<!ENTITY esblink "../../esb_ref_guide/html_single/index.html"> +<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html"> +<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html"> +<!ENTITY jbpmlink "../../jbpm/html_single/index.html"> +<!ENTITY jsflink "../../jsf/html_single/index.html"> +<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html"> +<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html"> +<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html"> +<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html"> + + +]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff"> + + <bookinfo> + <title>JBoss Server Manager Reference Guide</title> + + <author><firstname>Anatoly</firstname><surname>Fedosik</surname></author> + <author><firstname>Olga</firstname><surname>Chikvina</surname></author> + <author&gt;&lt;firstname&gt;Rob&lt;/firstname&gt;&lt;surname&gt;Stryker&lt;/surname&gt;&lt;email&gt;rob.stryker(a)jboss.com&lt;/email&gt;&lt;/author&gt; + <author&gt;&lt;firstname&gt;Svetlana&lt;/firstname&gt;&lt;surname&gt;Mukhina&lt;/surname&gt;&lt;email&gt;smukhina(a)exadel.com&lt;/email&gt;&lt;/author&gt; + + <pubdate>April 2008</pubdate> + <copyright> + <year>2007</year> + <year>2008</year> + <holder>JBoss, a division of Red Hat Inc.</holder> + </copyright> + <releaseinfo> + Version: <diffmk:wrapper diffmk:change="changed">3.0.0.beta1 + </diffmk:wrapper></releaseinfo> +<abstract diffmk:change="added"> + <title diffmk:change="added"></title> + <para diffmk:change="added"> + <ulink diffmk:change="added" url="http://download.jboss.org/jbosstools/nightly-docs/en/as/pdf/AS_... diffmk:change="added">PDF version</diffmk:wrapper></ulink> + </para> +</abstract> + + + </bookinfo> + + + <toc></toc> + +<chapter id="quick_start" revisionflag="added" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/as/docs/reference/en/modules/quick_start.xml"> + <title>Quick Start with JBoss Server</title> + + <para>This chapter covers the basics of working with the JBoss server. If you already have + installed JBoss server and runtime you can quickly learn how to configure, start, stop the + server, to know deployment and archiving processes. How to install runtimes and servers read in + the <link linkend="runtimes_servers">Runtimes and Servers in the JBoss AS plugin</link> chapter.</para> + + <para>To start working with JBoss AS, select a <property moreinfo="none">JBoss AS Perspective</property> via + <emphasis><property moreinfo="none">Window &gt; Open Perspective &gt; Other &gt; JBoss AS</property>.</emphasis></para> + + <section id="starting"> + <title>Starting JBoss server</title> + + <para>Starting JBoss server is quite simple. You can control the server behaviour with the help + of a special toolbar in the <property moreinfo="none">JBoss Server View</property> where you could + <property moreinfo="none">start</property> it in a regular or debug mode, <property moreinfo="none">stop</property> it or + <property moreinfo="none">restart</property> it, <property moreinfo="none">publish</property> to the server.</para> + + <figure float="0"> + <title>JBoss Server Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>To launch the server click the green-with-white-arrow icon on the <property moreinfo="none">JBoss Server + View </property>or right click server name in this view and select <emphasis> + <property moreinfo="none">Start</property> + </emphasis>. If this view is not open, select <emphasis><property moreinfo="none">Window &gt; Show View + &gt; Other &gt; Server &gt; JBoss Server View</property>.</emphasis></para> + + <figure float="0"> + <title>Start JBoss Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </section> + + <section id="stopping"> + <title>Stopping JBoss Server</title> + + <para>To stop the server, click the <property moreinfo="none">Stop</property> icon in JBoss Server View or right + click the server name and press <property moreinfo="none">Stop</property>.</para> + + <figure float="0"> + <title>Stop JBoss Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>When the server is stopped you will see <property moreinfo="none">Stopped</property> next to its name in + the State column.</para> + <para>Learn more about the JBoss Server View <link linkend="JBossServerView">here</link>.</para> + </section> + + <section id="archiving"> + + <title>Project Archiving</title> + + <para>JBoss Tools comes with our own archives tool. The Project Archives plugin consists + primarily of a view to set up each packaging configuration (<emphasis> + <property moreinfo="none">Window &gt; Show View &gt; Other &gt; JBoss Tools &gt; Project archives</property> + </emphasis>).</para> + <para>Right clicking in the <property moreinfo="none">Project Archives View</property> you can create War, EJB + War or EAR archive.</para> + + <figure float="0"> + <title>Archive Creating</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Using the context menu on the item you can initiate a full <property moreinfo="none">build</property> on + archive, <property moreinfo="none">edit</property>, <property moreinfo="none">delete</property> or + <property moreinfo="none">publish</property> it.</para> + + <figure float="0"> + <title>Context Menu on the Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_8.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Learn more about the <property moreinfo="none">Project Archives View</property> + <link linkend="Project_archivesView">here</link>.</para> + + </section> + <section id="deployment"> + <title>Deploying an Application to a Server</title> + + <para>There are two times to deploy your application:</para> + <itemizedlist> + <listitem> + <para>While creating it</para> + </listitem> + <listitem> + <para>After it already exists</para> + </listitem> + </itemizedlist> + + <para>When you create a new project (Seam, JSF or Struts) with the New Project or Import Project + wizards, the one of wizards steps has a <emphasis> + <property moreinfo="none">Target Runtime</property> + </emphasis> and <emphasis> + <property moreinfo="none">Target Server</property> + </emphasis> sections. You can deploy the application through the appropriate selection in + these sections.</para> + + <figure float="0"> + <title>Runtime and Server Sections in the New Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_4a.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <figure float="0"> + <title>Runtime and Server Sections in the Import Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_4b.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>You can deploy an existing application to a server by right-clicking the target defined + server in the <property moreinfo="none">JBoss Servers View</property> and then selecting <property moreinfo="none">Add and + Remove Projects</property> from the context menu.</para> + + <figure float="0"> + <title>Add and Remove Projects From the Context Menu.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>If this application is not assigned to a server, it will be in the left-hand available + projects list. Clicking on the <property moreinfo="none">Add &gt;</property> button will add it to the right-hand + configured projects list and deploy the application to this server.</para> + + <figure float="0"> + <title>Modifying The Projects that are Configured on the Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Here, we have just performed the basic steps you should know to quick start with JBoss + server. In fact, there are more functionalities which you can make use of. Further we will talk about them in detail.</para> + </section> + + + <section> + <title>Other relevant resources on the topic</title> + + <para>All JBoss Developer Studio/JBoss Tools documentation you can find <ulink url="http://docs.jboss.org/tools/2.1.0.GA">here</ulink>... + <para>The latest documentation builds are available <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">her... + + </section> + +</chapter> + + +<chapter id="runtimes_servers" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/as/docs/reference/en/modules/runtimes_servers.xml" xreflabel="runtimes_servers"> + <?dbhtml filename="runtimes_servers.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>Deploy</keyword> + <keyword>Deployment</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> + <title>Runtimes and Servers in the JBoss AS plugin</title> + + <para>In this chapter we will discuss how to install runtimes and servers.</para> + + <para>First of all it's 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 moreinfo="none">runtime</property> and <property moreinfo="none">server</property> instances.</para> + + <section> + <title>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 then be used for + two primary purposes:</para> + <itemizedlist> + <listitem> + <para>it provides classpath additions to WTP projects that require them.</para> + </listitem> + <listitem> + <para>for <property moreinfo="none">JBoss server</property> 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 id="InstNewRuntime"> + <title>Installing a new Runtime</title> + <para>You can install runtimes into eclipse from the <emphasis> + <property moreinfo="none">Window &gt; Preferences... </property> + </emphasis> menu, and then select <emphasis> + <property moreinfo="none">Server &gt; Installed Runtimes</property> + </emphasis> from the categories available.</para> + <figure float="0"> + <title>Installed Runtimes</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>From this preference page you can see all declared runtimes and their types as well. + Figure above shows two declared runtimes that include a JBoss 4.2 instance. Here, + it's possible to edit or remove existing runtimes as well as add a new one.</para> + + <para>To create a JBoss runtime click <emphasis> + <property moreinfo="none">Add</property> + </emphasis> button and choose a necessary type of runtime from the appeared dialog. </para> + + <figure float="0"> + <title>Adding a Runtime</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>As you can see, <property moreinfo="none">JBoss Tools</property> provide its own adapters such as JBoss + 3.2, 4.0, 4.2 and 5.0 as well. The last one comes with its own new feature, that is a safer + incremental deployment, which prevents partial deployments to be picked up by the server. It + means that scanning for auto-deployment is suspended while files are being copied to the + deployment location and resumed when the copy is completed.</para> + + <note> + <title>Note:</title> + <para>Currently we recommend you to use a fully supported JBoss 4.2 server adapter.</para> + </note> + + <para>You'll also note a Deploy-Only Runtime type. This type provides no classpath + for WTP projects. It is used solely by its 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 float="0" id="add_runtime_figure"> + <title>Adding a JBoss 4.2 Runtime</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>The following table describes all the available options of the wizard.</para> + <table> + <title>Server Runtime Wizard Parameters</title> + <tgroup cols="2"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec colnum="2" colwidth="3*"></colspec> + + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> + + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + + <tbody> + <row> + <entry> + <para>Name</para> + </entry> + <entry> + <para>The name of a new Runtime for a chosen server. We suggest that you + don't leave a default value. It's better to give descriptive + names that will help to distinguish one runtime from another.</para> + </entry> + </row> + + <row> + <entry> + <para>Home directory</para> + </entry> + <entry> + <para>The path to a directory where the runtime is installed.</para> + </entry> + </row> + + <row> + <entry> + <para>jRE</para> + </entry> + <entry> + <para>The proper Java Runtime Environment. Because of the open-source nature of + JBoss, a user is likely to want to modify and repackage some of the + configuration-specific jboss jars and create their own configuration. Thus, rather + than forcing you to copy his entire JBoss installation, the structure of the + wizard allows to create only a new configuration instead.</para> + </entry> + </row> + + <row> + <entry> + <para>Configuration</para> + </entry> + <entry> + <para>The list of configurations (all, default, minimal) that is updated as soon as + you browse to a valid runtime installation folder. After the runtime is created + the configuration becomes an unchanging property of that runtime. To compile + against a different configuration's jars, you will need to create a new runtime + from that configuration.</para> + </entry> + </row> + + </tbody> + </tgroup> + </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'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.</para> + + <para>Press <emphasis> + <property moreinfo="none">Finish</property> + </emphasis> to see your new runtime in the list.</para> + </section> + + </section> + + <section> + <title>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 the modules (jars, wars, etc) you deploy to the server and also allow you to undeploy + those modules (see <link linkend="run_on_server_wizard">Deploying with Run On Server + Wizard</link> section). </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.</para> + + <section revisionflag="changed"> + <title>Creating a New Server</title> + + <para>There are many ways to get to the new server wizard. One way is to use the old standard <emphasis> + <property moreinfo="none">File &gt; New &gt; Other... </property> + </emphasis> and then <emphasis> + <property moreinfo="none">Server</property> + </emphasis>. This should show the wizard like below.</para> + <figure float="0"> + <title>Adding a JBoss Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>A server object is that keeps track of things like command line arguments when starting + or stopping, and runtimes keep track of the location of the installation. Thus, each server + instance must be backed by an appropriate runtime. </para> + + <para>From the list of already declared runtimes in the combo box below the view it's + possible to select which runtime you want your server to be backed by. If there is no + runtime that matches your needs just press <emphasis> + <property moreinfo="none">Installed Runtimes... </property> + </emphasis> to bring up the familiar preference page like in <link linkend="InstNewRuntime"> + the previous section</link>. Here, it becomes possible to edit already existing runtime or + add a new one with necessary configuration.</para> + + <figure float="0"> + <title>Installed Server Runtime Environments</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_5a.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>If the server you want to create doesn't have any installed runtime yet, the combo box + and button will disappear.</para> + + <figure float="0"> + <title>Installed Server Runtime Environments</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_5b.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>In this case the next page in the wizard which has the same form as in <link linkend="add_runtime_figure">the previous section</link> 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 is + largely confirmational, giving you a chance to verify that you've selected the + appropriate runtime. It also allows to name the server appropriately. </para> + + <figure float="0"> + <title>Installed Server Runtime Environments</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Press <emphasis> + <property moreinfo="none">Finish</property> + </emphasis> to complete the process of the server creation.</para> + <para>Now that we've created our runtimes and servers, we can dwell on all services + and tools that JBoss Server Manager provides.</para> + </section> + + </section> + +</chapter> + + +<chapter id="perspective" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/as/docs/reference/en/modules/perspective.xml" xreflabel="perspective"> + <?dbhtml filename="perspective.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>Deploy</keyword> + <keyword>Deployment</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> + <title>JBoss AS Perspective</title> + + <para>This chapter tells how to manage installed JBoss Servers via <property moreinfo="none">JBoss AS + Perspective</property>.</para> + + <para>The <property moreinfo="none">JBoss AS Perspective</property> is similar to the <property moreinfo="none">Java + Perspective</property>, but it contains a few additional views. Two of the additional views + are standard views, specifically the <property moreinfo="none">Console View</property> and the + <property moreinfo="none">Properties View</property>. The other two views that are added are the + <property moreinfo="none">Project Archives View</property> and the <property moreinfo="none">JBoss Server + View</property>.</para> + + <section id="JBossServerView"> + <?dbhtml filename="JBossServerView.html"?> + <title>The JBoss Server View</title> + <para>Let's have a look at the <property moreinfo="none">JBoss Server View</property> and inspect + in detail all parts it consists of. </para> + + <para>The <property moreinfo="none">JBoss Server View</property> is based on the WTP view, Server View. The + top part of the <property moreinfo="none">JBoss Servers View</property> essentially embeds the original + Server View directly into it, making slight changes to the context menu. A second part + was added to provide additional information about the server selected in the top part. </para> + + <figure float="0"> + <title>The JBoss Server View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + + <para>The view's toolbar provides quick access to starting a server (in debug mode, run + mode, or profile mode), restarting a server, stopping a server, or publishing to a + server.</para> + <figure float="0"> + <title>The JBoss Server View Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_19.png"></imagedata> + </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><emphasis> + <property moreinfo="none">Start the server in profiling mode</property> + </emphasis> button allows to enable profiling actions for your application. For more + details on how to start using TPTP profiling with <property moreinfo="none">JBoss Tools</property> refer + to <link linkend="tptp_support">TPTP Support</link> chapter.</para> + + <para><emphasis> + <property moreinfo="none">Publish to the server</property> + </emphasis> button 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>Now, let's get to know with both of the <property moreinfo="none">JBoss Server + View</property> parts.</para> + + <section role="updated"> + <title>Top Part of the JBoss Server View</title> + <para>In the top part of the <property moreinfo="none">JBoss Server View</property> all declared servers + are represented as well as their current states, that is, whether they are started + or stopped. </para> + <figure float="0"> + <title>Server Publish Status</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_18.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>The top part also shows the server's publish status. The fallowing table + lists possible statuses.</para> + + <table> + <title>Server Publish Status</title> + <tgroup cols="2"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec colnum="2" colwidth="3*"></colspec> + + + <thead> + <row> + <entry align="center">Status</entry> + + <entry align="center">Description</entry> + </row> + </thead> + + <tbody> + <row> + <entry align="center"> + <para>Republish</para> + </entry> + + <entry align="center"> + <para>The status which allows you to see if changes are + awaiting</para> + </entry> + </row> + <row> + <entry align="center"> + <para>Publishing...</para> + </entry> + + <entry align="center"> + <para>The status which shows if changes are being updated</para> + </entry> + </row> + <row> + <entry align="center"> + <para>Synchronized</para> + </entry> + + <entry align="center"> + <para>The status which allows you to see if changes are + in-sync</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + + <para>By double-clicking on any server, an editor window will appear allowing you to + edit parts of that server. On the figure 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> + + <figure float="0"> + <title>Preferences Page for the Chosen Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_20.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">It should be pointed out that our server adapter by default tries to automatically + detect the ports it needs for integrating with a </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">JBoss server</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">. + Sometimes it can though be relevant to override this automatic detection if you are + using some custom configuration. For this purposes the </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Server Ports</diffmk:wrapper></property> + </emphasis> <diffmk:wrapper diffmk:change="added">section in the </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Server</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">The </diffmk:wrapper>editor</property> <diffmk:wrapper diffmk:change="added">is provided where the + port settings are configurable.</diffmk:wrapper></para> + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">The settings relating to </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Publishing</diffmk:wrapper></property> + </emphasis><diffmk:wrapper diffmk:change="added">, </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Timeouts</diffmk:wrapper></property> + </emphasis> <diffmk:wrapper diffmk:change="added">or </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Server Polling</diffmk:wrapper></property> + </emphasis><diffmk:wrapper diffmk:change="deleted">will </diffmk:wrapper><diffmk:wrapper diffmk:change="added">can </diffmk:wrapper>also <diffmk:wrapper diffmk:change="changed">be </diffmk:wrapper><diffmk:wrapper diffmk:change="added">adjusted here.</diffmk:wrapper></para> + + <para diffmk:change="added" id="com_line_arg"><diffmk:wrapper diffmk:change="added">In the </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Server editor</diffmk:wrapper></property><diffmk:wrapper diffmk:change="deleted">you </diffmk:wrapper><diffmk:wrapper diffmk:change="added">it's possible + </diffmk:wrapper>to modify <diffmk:wrapper diffmk:change="changed">the </diffmk:wrapper>server's launch <diffmk:wrapper diffmk:change="added">configuration as well.</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">configuration. </diffmk:wrapper>It's just + after clicking <emphasis> + <property moreinfo="none">Open launch configuration</property> + </emphasis> link. In the open window there are the tabs for setting command line + arguments and other things that are relevant to launching the server.</para> + + <figure float="0"> + <title>Launch Configuration Properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_22.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Look up <ulink url="http://docs.jboss.org/jbossas/guides/installguide/r1/en/html/st... to find parameters which can be specified for <property moreinfo="none">JBoss + Server</property>.</para> + + <para>As the JBoss Servers have few properties to modify in this editor, a shortcut to + the launch configuration has been provided in the context menu when right-clicking + on a server.</para> + + <figure float="0"> + <title>Twiddle Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_21.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>The following table describes all these additional properties.</para> + <table> + <title>Server Properties through the Context Menu</title> + <tgroup cols="2"> + <colspec align="left" colnum="1" colwidth="1*"></colspec> + <colspec colnum="2" colwidth="3*"></colspec> + + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> + + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + + <tbody> + <row> + <entry> + <para>New Server</para> + </entry> + <entry> + <para>The option allows to define a new server</para> + </entry> + </row> + + <row> + <entry> + <para>Delete</para> + </entry> + <entry> + <para>Standard option that allows to delete the chosen server</para> + </entry> + </row> + + <row> + <entry> + <para>Start</para> + </entry> + <entry> + <para>The action for stating a server in a run mode</para> + </entry> + </row> + + <row> + <entry> + <para>Debug</para> + </entry> + <entry> + <para>The action for stating a server in a debug mode</para> + </entry> + </row> + + <row> + <entry> + <para>Stop</para> + </entry> + <entry> + <para>The action for stopping a declared server</para> + </entry> + </row> + + <row> + <entry> + <para>Publish</para> + </entry> + <entry> + <para>The action for synching the publish information between the + server and workspace</para> + </entry> + </row> + + <row> + <entry> + <para>Clean</para> + </entry> + <entry> + <para>The option for complete redeploying the resources</para> + </entry> + </row> + + <row> + <entry> + <para>Twiddle Server</para> + </entry> + <entry> + <para>The option provides a dialog for running Twiddle commands + against the Twiddle Server</para> + </entry> + </row> + + <row> + <entry> + <para>Edit Launch Configuration</para> + </entry> + <entry> + <para>The option that provides an editor for editing launch + configuration properties of the proper server</para> + </entry> + </row> + + <row> + <entry> + <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> + </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> + </section> + + <section> + <title>Bottom Part of the JBoss Server View</title> + + <para>Here, we dwell on the bottom part of the <property moreinfo="none">JBoss Server View</property>.</para> + <para>First, we should say that the bottom part is meant to provide additional + functionality relevant to the server selected in the top part 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 bottom part of the <property moreinfo="none">JBoss Server + View</property>.</para> + + <figure float="0"> + <title>View Extensions</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>In order to access the view's preferences, you should access <emphasis> + <property moreinfo="none">Window &gt; Preferences &gt; JBoss Tools &gt; JBoss + Servers &gt; View</property> + </emphasis>. This preference page allows you to select which view extensions you + want on or off, the order they appear in the view, as well as any other + extension-specific preferences that may be available.</para> + + <figure float="0"> + <title>View Preferences</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_2.png" scale="75"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>The first view extension is <emphasis> + <property moreinfo="none">Modules</property> + </emphasis> section. It shows which modules are currently deployed to the server, + and allows you to remove them from the server, or force a full republish upon them. + It only shows which modules have been deployed through Eclipse, not any and all + modules that happen to be in the deploy directory.</para> + + <figure float="0"> + <title>Modules Action</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>The <emphasis> + <property moreinfo="none">Event Log</property> + </emphasis> 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 <emphasis> + <property moreinfo="none">Event Log</property> + </emphasis>. However, if the <property moreinfo="none">Properties View</property> is opened, you can + receive further information on each <emphasis> + <property moreinfo="none">Event Log</property> + </emphasis> item (when available).</para> + + <figure float="0"> + <title>Event Log Actions</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <figure float="0"> + <title>Starting the Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>The <emphasis> + <property moreinfo="none">XML Configuration</property> + </emphasis> category allows you to quickly browse to descriptor files in your + server's deploy directory and check or change the values. Its use requires the + <property moreinfo="none">Properties view</property>. Basically, <emphasis> + <property moreinfo="none">XML Configuration</property> + </emphasis> includes XML XPaths where a xpath is a path used to access some specific + part of an xml document. </para> + + <figure float="0"> + <title>XML Configuration and Properties View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <note> + <title>Note:</title> + <para>You are assumed to be familiar with XPath. If not, we highly suggested that + you look through an appropriate manual or tutorial on the topic.</para> + </note> + + <para>The <emphasis> + <property moreinfo="none">XML Configuration</property> + </emphasis> category itself contains only a list of categories. <emphasis> + <property moreinfo="none">Ports</property> + </emphasis> are provided by default and is filled with many of the most commonly + used ports in the <property moreinfo="none">JBoss Server</property>. In the <property moreinfo="none">Properties + view</property> you can see an identifier and nested files underneath in which + that xpath can be found as well as its current value. The details of the xpath are + hidden as all you need to see is only which file you're referring to and + what its current value is.</para> + + <para> By right-clicking on <emphasis> + <property moreinfo="none">XML Configuration</property>, </emphasis> you can create a new + category. Besides, context menu for <emphasis> + <property moreinfo="none">XML Configuration</property> + </emphasis> category makes possible to disable it. You can disable any category in + the bottom part of the <emphasis> + <property moreinfo="none">JBoss Server View</property>.</emphasis> Look for them in the <emphasis> + <property moreinfo="none">Inactive Categories</property> + </emphasis> afterwards to re-enable.</para> + + <figure float="0"> + <title>Adding New Category</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_8.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>By right-clicking on <emphasis> + <property moreinfo="none">Ports</property> + </emphasis> or any other category in <emphasis> + <property moreinfo="none">XML Configuration</property> + </emphasis>, you can create a new xpath.</para> + + <figure float="0"> + <title>Adding New XPath</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_9.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>After that, the dialog shown below will appear.</para> + + <figure float="0"> + <title>Adding New XPath</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_10.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>The goal here is to get an end result where the XPath matches up with a necessary + property. With that in mind, let's look how it works. If the property you + want to reach is the value of the <emphasis>name</emphasis> attribute in the element + <emphasis>&lt;mbean&gt;</emphasis>, then your <emphasis> + <property moreinfo="none">XPath Patten</property> + </emphasis>should end with <emphasis>mbean</emphasis> and your <emphasis> + <property moreinfo="none">Attribute Name</property> + </emphasis> should be <emphasis>name</emphasis> like on the next figure.</para> + + <programlisting format="linespecific" role="XML">... +&lt;server&gt; +... + &lt;mbean code="org.jboss.ejb.EJBDeployer" + name="jboss.ejb:service=EJBDeployer" xmbean-dd=""&gt; + + &lt;!-- Inline XMBean Descriptor BEGIN --&gt; + &lt;xmbean&gt; + &lt;description&gt; + The EJBDeployer responsible for ejb jar deployment&lt;/description&gt; + ... + &lt;/xmbean&gt; + &lt;/mbean&gt; +&lt;/server&gt; +</programlisting> + + <figure float="0"> + <title>XPath Preview</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_23.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <tip> + <title>Tip:</title> + <para>Notice, when you type the fields autocomplete to help you locate exactly what + xpath you're looking for.</para> + </tip> + + <para>Then, on the other hand, if your desired field is the text of an element + <emphasis>&lt;description&gt;</emphasis>, your <emphasis> + <property moreinfo="none">XPath Patten</property> + </emphasis> should end with <emphasis>description</emphasis> and <emphasis> + <property moreinfo="none">Attribute Name</property> + </emphasis> field should be left blank. When finished, click <emphasis> + <property moreinfo="none">Preview</property> + </emphasis> to see how many matches you have for that particular XPath.</para> + + <figure float="0"> + <title>XPath Preview</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_24.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>As part of the <property moreinfo="none">JBoss Server View</property> there is a <emphasis> + <property moreinfo="none">JMX Console</property> + </emphasis> section which allows you to browse and use the JMX exposed beans on the + server.</para> + <figure float="0"> + <title>JMX Console</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_17.png" scale="75"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <section> + <title>Relevant Resources Links</title> + <para>Find more about XPath in the <ulink url="http://www.w3.org/TR/xpath20/">XPath + Documentation</ulink>.</para> + </section> + </section> + + </section> + + <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 + Tools comes with our own Archives tool with a bit easier and less-verbose XML and a + handy user interface. The Project Archives plugin consists primarily of a view, that is + <property moreinfo="none">Project Archives View</property>, to set up each packaging configuration.</para> + <para>So far, let's look through all functionality that the <property moreinfo="none">Project + Archives View</property> provides.</para> + + <section id="archives_overview"> + <title>Overview</title> + + <para>The packaging configuration for each project is stored in the project's root + folder, and is in a file named <emphasis> + <property moreinfo="none">.packages</property> + </emphasis>, 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> + + <figure float="0"> + <title>Archives View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_25.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>A project's configuration contains archives. On the image above there is + only one archive, but a project can contain many. Inside the archive folders + (testFolder), filesets, or other internal archives can be located. Internal archives + and filesets may be directly inside of an archive, or in some sub-folder of that + archive.</para> + + <para>In the upper right corner of the view you can see an icon which, when clicked, + will build the selected top-level archive. Additionally, you can select <emphasis> + <property moreinfo="none">Project &gt; Build Packages</property> + </emphasis> when a project is selected in the <property moreinfo="none">Packages View</property> to + build all declared packages in that project's <emphasis> + <property moreinfo="none">.packages</property> + </emphasis> file. This will execute a full build on all declared archives.</para> + </section> + + <section id="Creating_Archive"> + <title>Creating an Archive</title> + <para>When creating a new archive, you have some different options at your disposal. If + the project has no <emphasis> + <property moreinfo="none">.packages</property> + </emphasis> file, your options will be presented to you all at once to choose from. + Otherwise you will right-click inside the view and select <emphasis> + <property moreinfo="none">New Archive</property> + </emphasis> to see your archive type options.</para> + <figure float="0"> + <title>Create an Archive</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_12.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <note diffmk:change="added"> + <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Note:</diffmk:wrapper></title> + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">If you see only JAR from the list of available archive types, you should + verify whether AS Tools plugins/features are in place. EAR, EJB JAR and WAR options are + contributed by the AS Tools independently from webtools and the virtual + project model. Thus, without them only JAR will show up.</diffmk:wrapper></para> + </note> + + <para><property moreinfo="none">JAR</property> 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 + <property moreinfo="none">WAR</property> archive, the archive will be created with a few + filesets relevant to the known structure of the project.</para> + + <para>Here is the first page of all New archive wizards. It is the same for any archive + type and the only page in the <property moreinfo="none">New Jar Wizard</property>.</para> + <figure float="0"> + <title>New JAR Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_13.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <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 + workspace, inside some other archive, or inside a folder declared inside an archive. + You can browse to workspace or filesystem destinations by clicking on their + respective buttons. To select a destination inside some other archive, you'll need + to press the <emphasis> + <property moreinfo="none">Workspace...</property> + </emphasis> button. At the bottom of the list, you'll see archives that + have been declared in the workspace.</para> + <section id="CreatingaFolder"> + <title>Creating a Folder</title> + <para>Creating a folder is much easier. You simply right-click on an archive or + folder you want your new folder to be a child under. The only piece of required + information is naming the file.</para> + </section> + <section id="CreatingaFileSet"> + <title>Creating a FileSet</title> + <para>To create a new fileset, you click on an available target location such as an + archive, a nested archive, or a folder within an archive, and select <emphasis> + <property moreinfo="none">New Fileset</property> + </emphasis>.</para> + <para>The <property moreinfo="none">New Fileset Wizard</property> requires a destination (where the + files will go), 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 float="0"> + <title>Adding a New FileSet</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_26.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Below that, the fileset requires only an includes pattern and an excludes + pattern. As you type in either of these fields, the preview viewer should update + itself with which files are matched.</para> + </section> + </section> + <section id="View_Actions"> + <title>Archive Actions</title> + <figure float="0"> + <title>Context Menu on the Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_14.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <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 align="left" colnum="1" colwidth="1*"></colspec> + <colspec colnum="2" colwidth="3*"></colspec> + + + <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>Publishing to Server</title> + <para>Finally, you'll need to publish your application to a server. Here, we + show you how to do it with the help of <emphasis> + <property moreinfo="none">Archives View</property> + </emphasis>.</para> + + <figure float="0"> + <title>Context Menu on the Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_15.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The dialog above appears after selecting <emphasis> + <property moreinfo="none">Publish To Server</property> + </emphasis>. To simply publish once, you just select the server(s) that you want, + and finish. If you want the <emphasis> + <property moreinfo="none">Publish to Server</property> + </emphasis> action on that particular Archive to publish always to that set of + servers, then check the appropriate checkbox. And finally, to enable automatic + publishing upon build events, check the last checkbox.</para> + <para>The automatic publishing feature is nice if, for example, your package's + destination (where it is built) is a temporary folder and you want the archive + published to several servers. If you only really want your archive published to one + server, it might be easier to have the archive's destination folder be the deploy + folder of the server.</para> + </section> + <section> + <title>Relevant Resources Links</title> + <para>Refer to <ulink url="http://ant.apache.org/manual/index.html">Ant manual</ulink> + to find more on how to build your applications with help of Ant.</para> + + <para>At this point, you are guessed to be familiar with <property moreinfo="none">JBoss AS + Perspective</property> and your next step now is to explore how to work with + different kinds of projects.</para> + </section> + + </section> + + +</chapter> + + +<chapter id="webtools" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/as/docs/reference/en/modules/webtools.xml"> + <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. Web projects of <property diffmk:change="added" moreinfo="none">JBoss Tools</property> are + Struts, JSF and Seam projects. All of them are called faceted projects. Thus, in this + chapter we are going to tell you about facets the main benefit of which to provide proper + structuring and packaging for any type of project.</para> + + <section> + <title>Faceted Projects Overview</title> + <para>The idea behind faceted projects is that each project can accept units of + functionality, or facets, which can be added or removed by the user. Most often, these + facets either add to the project's classpath, enable a builder, or watch the project in + some other fashion. Generally, every project concerned has at least one facet when + it's created. As an example, a Web project has a WebDoclet facet, or an EJB + Project has an EJB Module facet as prerequisites.</para> + + <para> WTP projects have undergone some criticism as being + <emphasis>over-engineered</emphasis> or too restrictive in their design. WTP projects + are set up in a tree-relationship to each other, where one project can be a child of + another. For example, an EAR project may have a Web Project child, an EJB project child, + or other types.</para> + + <para> However, the benefit of this is that the structure of your projects is then known, + and packaging it up *should* be trivial. Apparently, 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 <link linkend="Project_archivesView">Archives + plugin</link>.</para> + </section> + + + <section revisionflag="changed"> + <title>Adding Facets to a Project</title> + + <para><diffmk:wrapper diffmk:change="added">In</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">There are two ways to add facets to a project. </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">this section we're going </diffmk:wrapper>to <diffmk:wrapper diffmk:change="added">consider</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">include facets into + already existing project. For that you should bring up </diffmk:wrapper>the <diffmk:wrapper diffmk:change="added">facets</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">context menu for selected + project </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">added by + </diffmk:wrapper><property moreinfo="none"><diffmk:wrapper diffmk:change="added">JBoss</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Properties. + At this point, choose + </diffmk:wrapper><diffmk:wrapper diffmk:change="added">Tools</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Project Facets</diffmk:wrapper></property> + <diffmk:wrapper diffmk:change="deleted">from </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">and show how you can configure them in a project: add new ones or + </diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">give opportunity to </diffmk:wrapper>modify <diffmk:wrapper diffmk:change="added">already</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">it by </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">existing configuration </diffmk:wrapper><diffmk:wrapper diffmk:change="added">of + </diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Modify </diffmk:wrapper><diffmk:wrapper diffmk:change="added">the</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Project... + </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">facets.</diffmk:wrapper></para> + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">One + </diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Adding </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">way </diffmk:wrapper>to <diffmk:wrapper diffmk:change="added">configure</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">the Existing Project + + + + + + + + The </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">the facets </diffmk:wrapper>is <diffmk:wrapper diffmk:change="added">doing</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">adding necessary </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">it </diffmk:wrapper>while organizing a new project. To + demonstrate <diffmk:wrapper diffmk:change="changed">this </diffmk:wrapper>let's create a new <property moreinfo="none">Dynamic Web Project</property> <diffmk:wrapper diffmk:change="added">by + </diffmk:wrapper>selecting <diffmk:wrapper diffmk:change="deleted">as usual </diffmk:wrapper><emphasis> + <property moreinfo="none">File &gt; New &gt; Other...</property> + </emphasis> and then <emphasis> + <property moreinfo="none">Web &gt; Dynamic Web Project</property>. </emphasis></para> + <figure float="0"> + <title>New Dynamic Web Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/webtools/webtools_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Click <emphasis> + <property moreinfo="none">Next</property> + </emphasis> and you will see Dynamic Web Project <diffmk:wrapper diffmk:change="added">page</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">page. + + Faceted </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">like on the </diffmk:wrapper><diffmk:wrapper diffmk:change="added">figure below.</diffmk:wrapper></para> + + <diffmk:wrapper diffmk:change="deleted">Page + + + + + + + </diffmk:wrapper><para> The first page of most WTP projects allows you to target a specific runtime, + representing a server's library location. It will also provide you the ability to add + this project to an EAR project, and select a pre-selected default set of facets, called + a configuration, rather than manually select each facet you might want.</para> + <para> Selecting the runtime, again, allows the project to install the proper classpaths to + the project so it knows what code to compile against.</para> + + <figure float="0" id="dyn_web_project"> + <title><diffmk:wrapper diffmk:change="added">New</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Faceted Project </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">Dynamic Web Project</diffmk:wrapper></title> + <mediaobject> + <imageobject> + <imagedata fileref="images/webtools/webtools_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para><diffmk:wrapper diffmk:change="added">Click </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">on the </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Modify</diffmk:wrapper></property> + </emphasis><diffmk:wrapper diffmk:change="deleted">page </diffmk:wrapper><diffmk:wrapper diffmk:change="added">button next to </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Configuration</diffmk:wrapper></property> <diffmk:wrapper diffmk:change="added">section in</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">of </diffmk:wrapper><diffmk:wrapper diffmk:change="added">order to open + </diffmk:wrapper>the wizard <diffmk:wrapper diffmk:change="added">which </diffmk:wrapper>allows you to <diffmk:wrapper diffmk:change="changed">modify a chosen configuration. </diffmk:wrapper><diffmk:wrapper diffmk:change="added">The wizard looks</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">facets, </diffmk:wrapper>as + <diffmk:wrapper diffmk:change="added">follows.</diffmk:wrapper></para> + + <figure diffmk:change="added" float="0" id="project_facets"> + <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Project</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">described </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">Facets </diffmk:wrapper><diffmk:wrapper diffmk:change="added">Wizard</diffmk:wrapper></title> + <mediaobject diffmk:change="added"> + <imageobject diffmk:change="added"> + <imagedata diffmk:change="added" fileref="images/webtools/webtools_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">Here</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Some </diffmk:wrapper><diffmk:wrapper diffmk:change="added">part of the listed </diffmk:wrapper>facets <diffmk:wrapper diffmk:change="changed">are those which are provided by WTP. Some of </diffmk:wrapper><diffmk:wrapper diffmk:change="added">them are</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">but + </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">added by </diffmk:wrapper><property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">JBoss</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">whole </diffmk:wrapper><diffmk:wrapper diffmk:change="added">Tools</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">.</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">this </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">They </diffmk:wrapper><diffmk:wrapper diffmk:change="added">are:</diffmk:wrapper></para> + <itemizedlist diffmk:change="added"> + <listitem diffmk:change="added"> + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">BIRT</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">allows </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">Charting Runtime </diffmk:wrapper><diffmk:wrapper diffmk:change="added">Component</diffmk:wrapper></para> + </listitem> + <listitem diffmk:change="added"> + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">BIRT</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">add </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">Reporting Runtime </diffmk:wrapper><diffmk:wrapper diffmk:change="added">Component</diffmk:wrapper></para> + </listitem> + <listitem diffmk:change="added"> + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">JBoss</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">of </diffmk:wrapper><diffmk:wrapper diffmk:change="added">ESB</diffmk:wrapper></para> + </listitem> + <listitem diffmk:change="added"> + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">JBoss</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">facets </diffmk:wrapper><diffmk:wrapper diffmk:change="added">Portlets</diffmk:wrapper></para> + </listitem> + <listitem diffmk:change="added"> + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">JBoss</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">that </diffmk:wrapper><diffmk:wrapper diffmk:change="added">Web Services</diffmk:wrapper></para><diffmk:wrapper diffmk:change="deleted">don't + </diffmk:wrapper></listitem> + <listitem diffmk:change="added"> + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">Seam</diffmk:wrapper></para> + </listitem> + </itemizedlist> + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">On</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">conflict </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">this wizard page you can enable or disable any facet as well </diffmk:wrapper><diffmk:wrapper diffmk:change="added">as change it version.</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">that + </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">What you should note here is that some facets or facets versions </diffmk:wrapper><diffmk:wrapper diffmk:change="added">may conflict with each</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">and + </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">other. In case of incompatibility you'll be prompted about this in </diffmk:wrapper><diffmk:wrapper diffmk:change="added">the + </diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Show </diffmk:wrapper><diffmk:wrapper diffmk:change="added">combo + box underneath.</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Constraints.</diffmk:wrapper></para> + <figure float="0"> + <title>Facet Constraints</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/webtools/webtools_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para><diffmk:wrapper diffmk:change="added">When</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Notice that here it is also possible </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">switching on </diffmk:wrapper>the <emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Runtimes</diffmk:wrapper></property><diffmk:wrapper diffmk:change="deleted">version of any facet. If + </diffmk:wrapper></emphasis><diffmk:wrapper diffmk:change="deleted">the chosen version isn't compatible with </diffmk:wrapper><diffmk:wrapper diffmk:change="changed">tab on the right </diffmk:wrapper>you'll <diffmk:wrapper diffmk:change="added">see</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">be prompted + about this in </diffmk:wrapper>the <diffmk:wrapper diffmk:change="changed">currant Server Runtime.</diffmk:wrapper></para> + <figure float="0"> + <title><diffmk:wrapper diffmk:change="changed">Runtimes </diffmk:wrapper><diffmk:wrapper diffmk:change="added">on the Project Facets Wizard</diffmk:wrapper><diffmk:wrapper diffmk:change="deleted">Constraints</diffmk:wrapper></title> + <mediaobject> + <imageobject> + <imagedata fileref="images/webtools/webtools_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para><diffmk:wrapper diffmk:change="added">On this tab you can also create a new Server Runtime and make it primary by pressing </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Make Primary</diffmk:wrapper></property> + </emphasis> <diffmk:wrapper diffmk:change="added">button after enabling it.</diffmk:wrapper></para> + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">Clicking on </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">OK</diffmk:wrapper></property> + </emphasis> <diffmk:wrapper diffmk:change="added">will save the chosen configuration of the facets and return you to the </diffmk:wrapper><link diffmk:change="added" linkend="dyn_web_project"><diffmk:wrapper diffmk:change="added">Dynamic Web Project wizard</diffmk:wrapper></link><diffmk:wrapper diffmk:change="added">. </diffmk:wrapper>Further pages in the + wizard are specific to either the project <diffmk:wrapper diffmk:change="changed">type </diffmk:wrapper>or the facets selected.</para> + + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">If you need to configure the facets for the existing project, you should bring up the + context menu for selected project and click </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Properties</diffmk:wrapper></property> + </emphasis> <diffmk:wrapper diffmk:change="added">and then </diffmk:wrapper><emphasis diffmk:change="added"> + <property diffmk:change="added" moreinfo="none"><diffmk:wrapper diffmk:change="added">Project Facets</diffmk:wrapper></property><diffmk:wrapper diffmk:change="added">. </diffmk:wrapper></emphasis> <diffmk:wrapper diffmk:change="added">This will bring up the familiar + </diffmk:wrapper><link diffmk:change="added" linkend="project_facets"><diffmk:wrapper diffmk:change="added">Project Facets wizard</diffmk:wrapper></link><diffmk:wrapper diffmk:change="added">, where you can create + your own custom facets configuration.</diffmk:wrapper></para> + + <para diffmk:change="added"></para> + + </section> + <section diffmk:change="added" id="rel_resources_links"> + <title diffmk:change="added"><diffmk:wrapper diffmk:change="added">Relevant Resources Links</diffmk:wrapper></title> + + <para diffmk:change="added"><diffmk:wrapper diffmk:change="added">More on the WTP facets you can read in the </diffmk:wrapper><ulink diffmk:change="added" url="http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.j... diffmk:change="added">eclipse help</diffmk:wrapper></ulink><diffmk:wrapper diffmk:change="added">.</diffmk:wrapper></para> + </section> +</chapter> + + +<chapter id="modules" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/as/docs/reference/en/modules/modules.xml"> + <title>Deploying Modules</title> + + <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.</para> + + <section revisionflag="changed"> + <title>Deploying on the Package Explorer</title> + + <para>On the package explorer it is possible to publish either a project to a server or just + a signal file. Let's look at how to do this.</para> + <section id="run_on_server_wizard"> + <title>Deploying with Run On Server Wizard</title> + <para> The first WTP method is to right-click on a project, such as a Dynamic Web + project, EJB project, or EAR project and then select <emphasis> + <property moreinfo="none">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 float="0"> + <title>Define a New Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/modules/modules_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Click <emphasis> + <property moreinfo="none">Next</property> + </emphasis> button to see add or remove projects page where you can choose projects + to configure them on server.</para> + <figure float="0" id="add_rem_proj"> + <title>Add or Remove Projects</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/modules/modules_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>This page of the wizard also allows to undeploy modules from the server. For that + choose proper module(s) from the right and click <emphasis> + <property moreinfo="none"> &lt; Remove</property> + </emphasis>. 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 <emphasis> + <property moreinfo="none">.war</property> + </emphasis>, <emphasis> + <property moreinfo="none">.jar</property> + </emphasis>, or <emphasis> + <property moreinfo="none">.ear</property> + </emphasis> as appropriate, and then copies that file into the proper deploy + directory. For quicker smarter deployment, you will need to create archives using + the <link linkend="Project_archivesView">Project Archives view</link> and customize + packaging yourself.</para> + </section> + + <section id="single_file_deployment"> + <?dbhtml filename="DeployToServer.html"?> + <title>Deploying single files</title> + + <para>Sometimes it becomes necessary to deploy one or more files to a server. For + that in order not to do a full republish in the context menu of files a <emphasis><property moreinfo="none">Deploy To Server</property></emphasis> + option is provided that allows a single file deployment. To deploy these non-WTP files/projects + right click on the file (<emphasis> + <property moreinfo="none">-ds.xml</property></emphasis>, <emphasis> + <property moreinfo="none">.ear</property></emphasis>, <emphasis> + <property moreinfo="none">.jar</property></emphasis> etc.) and select <emphasis> + <property moreinfo="none">Deploy To Server</property> + </emphasis> and it will be automatically deployed.</para> + <figure float="0"> + <title>Deploy to Sever</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/modules/modules_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>The deployed files are listed side-by-side with other modules that are deployed to + the server.</para> + + <figure float="0"> + <title>Deployed files on the Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/modules/modules_7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </section> + + </section> + <section> + <title>Deploying with JBoss Server View</title> + <para>As it has been already mentioned <property moreinfo="none">JBoss Server View</property> contains two + parts: the top part that displays all defined servers and the bottom part which provides + categories with additional information. Thus, in this section we suggest two more ways + to deploy resources onto the server.</para> + <section> + <title>Top part of JBoss Server View</title> + <para>In the top part of the <property moreinfo="none">JBoss Servers View</property> like in the Servers + View you should right click on a server and select the <emphasis> + <property moreinfo="none">Add and Remove Projects</property> + </emphasis> menu item.</para> + <figure float="0"> + <title>Add and Remove Projects</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/modules/modules_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>This will bring up a <link linkend="add_rem_proj">familiar dialog</link> allowing + you to either publish projects or modules to a server, or remove them from the + server. If the selected module is a project like a Dynamic Web project, EJB project, + or EAR project, it will be published as through <emphasis> + <property moreinfo="none">Run on Server</property> + </emphasis> wizard, with a best-guess full package. If, however, the selected + element is an archive from the <link linkend="Project_archivesView">Project Archives + view</link>, it will be published according to the rules of that module + type.</para> + </section> + + <section> + <title>Bottom part of JBoss Server View</title> + <para>In the bottom part of <emphasis> + <property moreinfo="none">JBoss Server View</property> + </emphasis> there is a category called <emphasis> + <property moreinfo="none">Modules</property> + </emphasis> which should display all currently-published modules on the server. + Right-clicking on the desired module and selecting <emphasis> + <property moreinfo="none">Full Publish</property> + </emphasis> will force a full rebuild of the entire module.</para> + <figure float="0"> + <title>Full Publish</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/modules/modules_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>Here, <emphasis> + <property moreinfo="none">Incremental Publish</property> + </emphasis> is meant to enable publishing of only those parts where changes have + been made.</para> + </section> + </section> + <section> + <title>Deploying with Project Archives View</title> + <para>In the <property moreinfo="none">Project Archives View</property> you can right-click on any declared + archive and select the <emphasis> + <property moreinfo="none">Publish To Server</property> + </emphasis> element. For more on this subject, see <link linkend="PublishToServer">Publishing to Server</link> in the Project Archives View section.</para> + <figure float="0"> + <title>Publish to Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/modules/modules_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para> The only way to ensure an <emphasis> + <property moreinfo="none">Incremental Build</property> + </emphasis>, such as changes to one <emphasis> + <property moreinfo="none">.jsp</property>, </emphasis> + <emphasis> + <property moreinfo="none">.html</property>, </emphasis> or <emphasis> + <property moreinfo="none">.class</property> + </emphasis> file, is to enable the builder for that project. This is done by either + changing the global preferences for the <property moreinfo="none">Archives View</property>, or by + enabling project-specific preferences and ensuring the builder is on.</para> + + + + <para>The last chapter covers a variety of methods on how you can deploy needed modules onto a + server.</para> + </section> +</chapter> + + +<chapter id="tptp_support" role="new" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/as/docs/reference/en/modules/tptp_support.xml"> + <title>TPTP Support</title> + <para>This chapter provides an overview on how to enable TPTP Profiling for <property moreinfo="none">JBoss + AS</property> adapters in <property moreinfo="none">JBoss Tools</property>.</para> + + <section> + <title>TPTP Profiling</title> + + <para>To get TPTP profiling work on <property moreinfo="none">JBoss Application Server</property> you should + first download <ulink url="http://www.eclipse.org/downloads/download.php?file=/tptp/4.5.0/... 4.5.0 Runtime</ulink> and install it, i. e. just add the content of <emphasis> + <property moreinfo="none">plugins/features</property> + </emphasis> folders from downloaded directory to the same folders in your eclipse + installation directory.</para> + + <para>And now all profile actions should work for you. To start <property moreinfo="none">JBoss + AS</property> in profiling mode use <emphasis> + <property moreinfo="none">Start the server in profiling mode</property> + </emphasis> button or <emphasis> + <property moreinfo="none">Profile As &gt; Profile on Server</property> + </emphasis> option in the context menu of the project.</para> + + <figure float="0"> + <title>Start the Server in Profiling mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/tptp_support/tptp_support_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <para>To enable TPTP features in your workbench use <property moreinfo="none">Profiling and Logging + Perspective</property> that you can find in the list of proposed perspectives: <emphasis> + <property moreinfo="none">Window &gt; Open Perspective &gt; Other…</property> + </emphasis> + </para> + + <figure float="0"> + <title>Profiling and Logging Perspective</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/tptp_support/tptp_support_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + + <section> + <title>Relevant Resources Links</title> + <para>All additional information on TPTP(Test and Performance Tools Platform) you can find + in <ulink url="http://www.eclipse.org/tptp/home/downloads/4.5.0/documents/quic... documentation</ulink>.</para> + + + + <para>In summary, this reference should help you to start with <ulink url="http://www.jboss.org/jbossas">JBoss AS</ulink> and get to know with functionality + for work with it.</para> + </section> +</chapter> + + +</book> Modified: branches/jbosstools-3.0.0.Beta1/as/docs/reference/pom.xml =================================================================== --- branches/jbosstools-3.0.0.Beta1/as/docs/reference/pom.xml 2008-10-29 16:10:20 UTC (rev 11300) +++ branches/jbosstools-3.0.0.Beta1/as/docs/reference/pom.xml 2008-10-29 16:17:50 UTC (rev 11301) @@ -34,7 +34,7 @@ </dependencies> <configuration> - <sourceDocumentName>master.xml</sourceDocumentName> + <sourceDocumentName>master_output.xml</sourceDocumentName> <sourceDirectory>${pom.basedir}/en</sourceDirectory> <imageResource> <directory>${pom.basedir}/en</directory> Added: branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/en/master_output.xml =================================================================== --- branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/en/master_output.xml (rev 0) +++ branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/en/master_output.xml 2008-10-29 16:17:50 UTC (rev 11301) @@ -0,0 +1,423 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" +"http://www.docbook.org/xml/4.3/docbookx.dtd" + +[<!ENTITY jsf_struts SYSTEM "modules/jsf_struts.xml"> +<!ENTITY jsf_struts_war SYSTEM "modules/jsf_struts_war.xml"> +<!ENTITY introduction SYSTEM "modules/introduction.xml"> +<!ENTITY workspace SYSTEM "modules/workspace.xml"> + +<!ENTITY seamlink "../../seam/html_single/index.html"> +<!ENTITY aslink "../../as/html_single/index.html"> +<!ENTITY esblink "../../esb_ref_guide/html_single/index.html"> +<!ENTITY gsglink "../../GettingStartedGuide/html_single/index.html"> +<!ENTITY hibernatelink "../../hibernatetools/html_single/index.html"> +<!ENTITY jbpmlink "../../jbpm/html_single/index.html"> +<!ENTITY jsflink "../../jsf/html_single/index.html"> +<!ENTITY jsfreflink "../../jsf_tools_ref_guide/html_single/index.html"> +<!ENTITY jsftutoriallink "../../jsf_tools_tutorial/html_single/index.html"> +<!ENTITY strutsreflink "../../struts_tools_ref_guide/html_single/index.html"> +<!ENTITY strutstutoriallink "../../struts_tools_tutorial/html_single/index.html"> +<!ENTITY migrationlink "../../Exadel-migration/html_single/index.html"> + +]><book xmlns:diffmk="http://diffmk.sf.net/ns/diff"> + <bookinfo> + <title>Exadel Studio Migration Guide</title> + + <pubdate>April 2008</pubdate> + <copyright> + <year>2007</year> + <year>2008</year> + <holder>JBoss, a division of Red Hat Inc.</holder> + </copyright> + <releaseinfo> +Version: 1.1.0.GA +</releaseinfo> + +<abstract diffmk:change="added"> + <title diffmk:change="added"></title> + <para diffmk:change="added"> + <ulink diffmk:change="added" url="http://download.jboss.org/jbosstools/nightly-docs/en/Exadel-mig... diffmk:change="added">PDF version</diffmk:wrapper></ulink> + </para> +</abstract> + + + + </bookinfo> + + <toc></toc> + +<chapter id="introduction" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/documentation/guides/Exadel-migration/en/modules/introduction.xml" xreflabel="introduction"> + <?dbhtml filename="introduction.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>JBDS</keyword> + <keyword>Exadel Studio Pro</keyword> + </keywordset> + </chapterinfo> + + <title>Introduction </title> + <para>This document is intended to help you to migrate an existing Exadel JSF or Struts projects + into <property moreinfo="none">JBoss Developer Studio</property>. Preferences can be exported from Eclipse 3.2.0 (3.2.1 or 3.2.2) and imported in Eclipse 3.3 by the standard Eclipse means. + </para> +<section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools documentation you can find <ulink url="http://docs.jboss.org/tools">here</ulink>.</pa... + <para>The latest documentation builds are available <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">her... + +</section> + + </chapter> + + +<chapter id="workspace" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/documentation/guides/Exadel-migration/en/modules/workspace.xml" xreflabel="workspace"> + <?dbhtml filename="workspace.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>JBDS</keyword> + <keyword>Exadel Studio Pro</keyword> + </keywordset> + </chapterinfo> + + <title>Migrate workspace</title> + <para>You will not be able to run projects in JBoss Developer Studio + using <property moreinfo="none">Exadel Studio workspace</property>. In this case, project capabilities and settings specified in Exadel Studio will be lost. The simplest way to avoid this, is to copy your projects in <property moreinfo="none">JBoss Developer Studio workspace</property> and make an import as it is described in the following chapters.</para> +</chapter> + + +<chapter id="jsf_struts" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/documentation/guides/Exadel-migration/en/modules/jsf_struts.xml" xreflabel="jsf_struts"> + <?dbhtml filename="jsf_struts.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>JBDS</keyword> + <keyword>Exadel Studio Pro</keyword> + <keyword>Migration</keyword> + </keywordset> + </chapterinfo> + + <title>Migration of JSF and Struts Projects</title> + <para>In this chapter you can find concise description of migration of JSF and Struts Projects.</para> + <section id="import_jsf"> + <title>JSF</title> + <para>JBoss Developer Studio includes an Import <property moreinfo="none">JSF Project</property> Wizard that radically simplifies the process of bringing your existing JSF applications + into your JBoss Developer Studio workspace as JSF projects. You just need to follow these four steps:</para> + <itemizedlist> + <listitem><para><emphasis><property moreinfo="none">Select File &gt; Import...</property></emphasis> from the menu bar, and then select <emphasis><property moreinfo="none">Other &gt; JSF Project </property></emphasis>from the Import dialog box that appears.</para></listitem> + </itemizedlist> + + <figure float="0"> + <title>Selecting the Import Menu Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <figure float="0"> + <title>Selecting the Import JSF Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>In the first screen of the wizard, select the <emphasis><property moreinfo="none">Change...</property></emphasis> button next to the <emphasis><property moreinfo="none">web.xml Location</property></emphasis> field. Browse to the location of the web.xml file for the application you + want to import as a <property moreinfo="none">JSF project</property>. Once you select it, you'll be returned to the dialog box to see a project name derived from the web.xml file you selected. + You can edit this project name, if you wish.</para></listitem> + </itemizedlist> + + <figure float="0"> + <title>Selecting the Web.xml File in the Project Location Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist id="import_jsf_screen"> + <listitem><para>In the <emphasis><property moreinfo="none">Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property moreinfo="none">Finish</property></emphasis> button.</para></listitem> + </itemizedlist> + <para>On this step JBoss Developer Studio will try to determine your project + structure and set the values for: <emphasis><property moreinfo="none">Web Root</property></emphasis>, <emphasis><property moreinfo="none">Source Folder</property></emphasis>, <emphasis><property moreinfo="none">Classes Folder</property></emphasis>, <emphasis><property moreinfo="none">Lib Folder</property></emphasis>. If your project has a custom structure, some values might not be + set. If this is the case, you can manually set those values by clicking the <emphasis><property moreinfo="none">Change...</property></emphasis> button.</para> + <para>After dealing with these settings, you have to work through a few more configuration settings. These settings deal primarily with how the project will be deployed within JBoss Developer Studio.</para> + <para>First, if the project you are importing is not already a JSF project, select the <emphasis><property moreinfo="none">Add Libraries</property></emphasis> check box to add all the JSF-related libraries to your project. </para> + <para>Then, you may select the JavaServer Faces implementation (<emphasis><property moreinfo="none">Environment</property></emphasis>) and <emphasis><property moreinfo="none">Servlet Version</property></emphasis>.</para> + <para>The <emphasis><property moreinfo="none">Context Path</property></emphasis> is the name under which the application will be deployed. </para> + <para>The <emphasis><property moreinfo="none">Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build the project. It is not possible to finish the importing of a project without selecting a Runtime. If you don't have any choices displayed for this, select <emphasis><property moreinfo="none">New...</property></emphasis> to add a new Runtime.</para> + <para>Finally, <emphasis><property moreinfo="none">Target Server</property></emphasis> sets the server to deploy the application under. The Target Server corresponds to the Runtime value selected above. If you don't want to deploy the application, uncheck this value.</para> + + + <figure float="0"> + <title>The Project Folders Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> + </itemizedlist> + + <figure float="0"> + <title>Imported Project in the Package Explorer View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </section> + <section> + <title>Struts</title> + <itemizedlist> + <listitem><para><emphasis><property moreinfo="none">Select File &gt; Import...</property></emphasis> from the menu bar, and then select <emphasis><property moreinfo="none">Other &gt; Struts Project</property></emphasis> from the Import dialog box that appears.</para></listitem> + </itemizedlist> + + <figure float="0"> + <title>Selecting the Import Menu Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <figure float="0"> + <title>Selecting the Import Struts Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_6.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>In the Project Location screen of the wizard, select the <emphasis><property moreinfo="none">Change... </property></emphasis>button next to the <emphasis><property moreinfo="none">web.xml Location</property></emphasis> field. Browse the location of the web.xml file for the application you + want to import as a <property moreinfo="none">Struts project</property>. Once you select it, you'll be returned to the dialog box to see a project name derived from the web.xml file you selected. + You can edit this project name, if you wish.</para></listitem> + </itemizedlist> + + <figure float="0"> + <title>The Project Location Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_10.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>In the next screen, JBoss Developer Studio will try to determine your project structure. The upper pane shows the modules in this project. + The lower pane allows you to edit the details of the select module. If the project structure is non-standard, some values might be left blank. + You can edit any values by hand or by using the <emphasis><property moreinfo="none">Change...</property></emphasis> button.</para></listitem> + </itemizedlist> + + <figure float="0"> + <title>The Project Modules Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>In the <emphasis><property moreinfo="none">Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property moreinfo="none">Finish</property></emphasis> button.</para> + </listitem> + </itemizedlist> + <para>On this step JBoss Developer Studio will try to determine your project structure and set the values for: <emphasis><property moreinfo="none">Classes Folder</property></emphasis>, <emphasis><property moreinfo="none">Lib Folder</property></emphasis>, and <emphasis><property moreinfo="none">Ant Build File</property></emphasis>. If your project has a custom structure, some values might not be set. If this is the case, you can manually set those values by clicking <emphasis><property moreinfo="none">Change</property></emphasis>.</para> + <para>After dealing with these settings, you have to work through a few more configuration settings. These settings deal primarily with how the project will be deployed within JBoss Developer Studio.</para> + <para>First, if the project you are importing is not already a Struts project, select the <emphasis><property moreinfo="none">Add Libraries</property></emphasis> check box to add all the Struts-related libraries to your project. </para> + <para>Then, you may select the Struts <emphasis><property moreinfo="none">Environment</property></emphasis> and <emphasis><property moreinfo="none">Servlet Version</property></emphasis>.</para> + <para>The <emphasis><property moreinfo="none">Context Path</property></emphasis> is the name under which the application will be deployed. </para> + <para>The <emphasis><property moreinfo="none">Runtime</property></emphasis> value tells Eclipse where to find Web libraries in order to build the project. It is not possible to finish the importing of a project without selecting a Runtime. If you don't have any choices displayed for this, select<emphasis><property moreinfo="none"> New...</property></emphasis> to add a new Runtime.</para> + <para>Finally, <emphasis><property moreinfo="none">Target Server</property></emphasis> sets the server to deploy the application under. The Target Server corresponds to the Runtime value selected above. If you don't want to deploy the application, uncheck this value.</para> + + + <figure float="0"> + <title>The Project Folders Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_8.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> + </itemizedlist> + + <figure float="0"> + <title>Imported Project in the Package Explorer View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_9.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </section> +</chapter> + + +<chapter id="jsf_struts_war" xml:base="file:///home/ochikvina/WORK/for_compare/trunk/documentation/guides/Exadel-migration/en/modules/jsf_struts_war.xml" xreflabel="jsf_struts_war"> + <?dbhtml filename="jsf_struts_war.html"?> + + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + + <keyword>JBDS</keyword> + + <keyword>Exadel Studio Pro</keyword> + </keywordset> + </chapterinfo> + + <title>Migrate JSF and Struts projects from *.war file</title> + <para>After you familiarized oneself with last chapter you can read this chapter. It looks as if you read in last chapter.</para> + <section> + <title>JSF</title> + + <itemizedlist> + <listitem> + <para>Select <emphasis><property moreinfo="none">File &gt; Import...</property></emphasis> from the menu bar, and then select + <emphasis><property moreinfo="none">Other &gt; JSF Project From *.war</property></emphasis> from the Import dialog box that + appears.</para> + </listitem> + </itemizedlist> + + <figure float="0"> + <title>Selecting the Import Menu Item</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <figure float="0"> + <title>Selecting the JSF Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>In the wizard screen, select the <emphasis><property moreinfo="none">Change...</property></emphasis> button next to + the <emphasis><property moreinfo="none">*.war Location</property></emphasis> field. Browse to the location of the *.war file for + the application you want to import as a JSF project. Once you select + it, you'll be returned to the dialog box to see a project name + derived from the *.war file you selected. You can edit this name, if + you wish.</para> + + <para>Uncheck the <emphasis><property moreinfo="none">Use Default Path</property></emphasis> check box if you want to import + your project outside of the Eclipse workspace. In this case, you would + use <emphasis><property moreinfo="none"> Change... </property></emphasis> button next to the <emphasis><property moreinfo="none">Location</property></emphasis> field to choose a + location.</para> + + <para><emphasis><property moreinfo="none">Context Path</property></emphasis> is the name under which the application will be + deployed.</para> + + <para>The <emphasis><property moreinfo="none">Runtime</property></emphasis> value tells Eclipse where to find Web libraries in + order to build the project. It is not possible to finish project + import without selecting Runtime. If you don't have any options + here, select <emphasis><property moreinfo="none">New...</property></emphasis> to add a new Runtime.</para> + + <para>Finally, <emphasis><property moreinfo="none">Target Server</property></emphasis> sets the server to deploy the application + under. The Target Server corresponds to the Runtime value selected + above. If you don't want to deploy the application, uncheck this + value.</para> + </listitem> + </itemizedlist> + + <figure float="0"> + <title>The JSF Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>Click on the <emphasis><property moreinfo="none">Finish</property></emphasis> button.</para> + </listitem> + </itemizedlist> + </section> + + <section> + <title>Struts</title> + + <itemizedlist> + <listitem> + <para>Select <emphasis><property moreinfo="none">File &gt; Import...</property></emphasis> from the menu bar, and then select + <emphasis><property moreinfo="none">Other &gt; Struts Project From *.war</property></emphasis> from the Import dialog box that + appears.</para> + </listitem> + </itemizedlist> + + <figure float="0"> + <title>Selecting the Import Menu Item</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <figure float="0"> + <title>Selecting the Struts Project From *.war Import Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>Follow the same steps as with the JSF Project From <property moreinfo="none">*.war</property> import + wizard.</para> + </listitem> + </itemizedlist> + + <figure float="0"> + <title>The Struts Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>Click on the <emphasis><property moreinfo="none">Finish</property></emphasis> button.</para> + </listitem> + </itemizedlist> + <para>The migration process is completed</para> + </section> +</chapter> + + +</book> Modified: branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/pom.xml =================================================================== --- branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/pom.xml 2008-10-29 16:10:20 UTC (rev 11300) +++ branches/jbosstools-3.0.0.Beta1/documentation/guides/Exadel-migration/pom.xml 2008-10-29 16:17:50 UTC (rev 11301) @@ -37,7 +37,7 @@ </dependency> </dependencies> <configuration> - <sourceDocumentName>master.xml</sourceDocumentName> + <sourceDocumentName>master_output.xml</sourceDocumentName> <sourceDirectory>${pom.basedir}/en</sourceDirectory> <imageResource> <directory>${pom.basedir}/en</directory>