Author: ykryvinchanka Date: 2007-11-09 08:47:25 -0500 (Fri, 09 Nov 2007) New Revision: 4822 Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/ trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration1.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_2.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_21.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_3.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_4.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_5.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration3.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration4.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration5.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/ trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration1.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war1.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_1.png trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_2.png trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml Removed: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration1.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_2.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_21.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_3.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_4.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_5.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration3.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration4.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration5.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war1.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_1.png trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_2.png trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml Modified: trunk/documentation/guides/userguide/Exadel-migration/en/master.xml Log: http://jira.jboss.com/jira/browse/RHDS-298 xml files names made shorter, used only lower case and _ to seperate words + new structure for images folders Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration1.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_2.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_21.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_21.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_3.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_4.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_5.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration2_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration3.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration4.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration5.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts/migration5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration1.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war1.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_1.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_2.png =================================================================== (Binary files differ) Property changes on: trunk/documentation/guides/userguide/Exadel-migration/en/images/jsf_struts_war/migration_war2_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration1.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_2.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_21.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_3.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_4.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration2_5.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration3.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration4.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration5.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war1.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_1.png =================================================================== (Binary files differ) Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/images/migration_war2_2.png =================================================================== (Binary files differ) Modified: trunk/documentation/guides/userguide/Exadel-migration/en/master.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/master.xml 2007-11-09 12:09:16 UTC (rev 4821) +++ trunk/documentation/guides/userguide/Exadel-migration/en/master.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -2,10 +2,10 @@ <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" "../../../resources/support/docbook-dtd/docbookx.dtd" -[<!ENTITY migration SYSTEM "modules/migration.xml"> -<!ENTITY migrationwar SYSTEM "modules/migration_war.xml"> -<!ENTITY intro_migration SYSTEM "modules/intro_migration.xml"> -<!ENTITY migration_ws SYSTEM "modules/migration_ws.xml"> +[<!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"> ]> <book> @@ -21,10 +21,10 @@ </bookinfo> <toc/> -&intro_migration; -&migration_ws; -&migration; -&migrationwar; +&introduction; +&workspace; +&jsf_struts; +&jsf_struts_war; </book> Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml 2007-11-09 12:09:16 UTC (rev 4821) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/intro_migration.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -1,17 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="intro_migration" xreflabel="intro_migration"> - <?dbhtml filename="intro_migration.html"?> - <chapterinfo> - <keywordset> - <keyword>Red Hat Developer Studio</keyword> - <keyword>RHDS</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>Red Hat 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> - - </chapter> Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml (rev 0) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/introduction.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -0,0 +1,17 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="introduction" xreflabel="introduction"> + <?dbhtml filename="introduction.html"?> + <chapterinfo> + <keywordset> + <keyword>Red Hat Developer Studio</keyword> + <keyword>RHDS</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>Red Hat 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> + + </chapter> Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml (rev 0) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -0,0 +1,182 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="jsf_struts" xreflabel="jsf_struts"> + <?dbhtml filename="jsf_struts.html"?> + <chapterinfo> + <keywordset> + <keyword>Red Hat Developer Studio</keyword> + <keyword>RHDS</keyword> + <keyword>Exadel Studio Pro</keyword> + <keyword>Migration</keyword> + </keywordset> + </chapterinfo> + + <title>Migration of JSF and Struts Projects</title> + <section> + <title>JSF</title> + <para>Red Hat Developer Studio includes an Import <property>JSF Project</property> Wizard that radically simplifies the process of bringing your existing JSF applications + into your Red Hat Developer Studio workspace as JSF projects. You just need to follow these four steps:</para> + <orderedlist> + <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > JSF Project </property></emphasis>from the Import dialog box that appears.</para></listitem> + </orderedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration1.png"/> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the Import JSF Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration2.png"/> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem><para>In the first screen of the wizard, select the <emphasis><property>Change...</property></emphasis> button next to the web.xml Location field. Browse to the location of the web.xml file for the application you + want to import as a <property>JSF project</property>. Once you select it, you&apos;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> + </orderedlist> + + <figure> + <title>Selecting the Web.xml File in the The Project Location Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration3.png"/> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para></listitem> + </orderedlist> + <para>On this step Red Hat Developer Studio will try to determine your project + structure and set the values for: <emphasis><property>Web Root</property></emphasis>, <emphasis><property>Source Folder</property></emphasis>, <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>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>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 Red Hat Developer Studio.</para> + <para>First, if the project you are importing is not already a JSF project, select the <emphasis><property>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>Environment</property></emphasis>) and <emphasis><property>Servlet Version</property></emphasis>.</para> + <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para> + <para>The <emphasis><property>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&apos;t have any choices displayed for this, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para> + <para>Finally, <emphasis><property>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&apos;t want to deploy the application, uncheck this value.</para> + + + <figure> + <title>The Project Folders Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration4.png"/> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> + </orderedlist> + + <figure> + <title>Imported Project in the Package Explorer View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration5.png"/> + </imageobject> + </mediaobject> + </figure> + + </section> + <section> + <title>Struts</title> + <orderedlist> + <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > Struts Project</property></emphasis> from the Import dialog box that appears.</para></listitem> + </orderedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration1.png"/> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the Import Struts Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration2_2.png"/> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem><para>In the Project Location screen of the wizard, select the <emphasis><property>Change... </property></emphasis>button next to the web.xml Location field. Browse the location of the web.xml file for the application you + want to import as a <property>Struts project</property>. Once you select it, you&apos;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> + </orderedlist> + + <figure> + <title>The Project Location Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration2_21.png"/> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem><para>In the next screen, Red Hat 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>Change...</property></emphasis> button.</para></listitem> + </orderedlist> + + <figure> + <title>The Project Modules Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration2_3.png"/> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para> + </listitem> + </orderedlist> + <para>On this step Red Hat Developer Studio will try to determine your project structure and set the values for: <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>Lib Folder</property></emphasis>, and <emphasis><property>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>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 Red Hat Developer Studio.</para> + <para>First, if the project you are importing is not already a Struts project, select the <emphasis><property>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>Environment</property></emphasis> and <emphasis><property>Servlet Version</property></emphasis>.</para> + <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para> + <para>The <emphasis><property>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&apos;t have any choices displayed for this, select<emphasis><property> New...</property></emphasis> to add a new Runtime.</para> + <para>Finally, <emphasis><property>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&apos;t want to deploy the application, uncheck this value.</para> + + + <figure> + <title>The Project Folders Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration2_4.png"/> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> + </orderedlist> + + <figure> + <title>Imported Project in the Package Explorer View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration2_5.png"/> + </imageobject> + </mediaobject> + </figure> + + </section> +</chapter> Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml (rev 0) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/jsf_struts_war.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -0,0 +1,148 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="jsf_struts_war" xreflabel="jsf_struts_war"> + <?dbhtml filename="jsf_struts_war.html"?> + + <chapterinfo> + <keywordset> + <keyword>Red Hat Developer Studio</keyword> + + <keyword>RHDS</keyword> + + <keyword>Exadel Studio Pro</keyword> + </keywordset> + </chapterinfo> + + <title>Migrate JSF and Struts projects from *.war file</title> + + <section> + <title>JSF</title> + + <orderedlist> + <listitem> + <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select + <emphasis><property>Other > JSF Project From *.war</property></emphasis> from the Import dialog box that + appears.</para> + </listitem> + </orderedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration1.png" /> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the JSF Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war1.png" /> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem> + <para>In the wizard screen, select the <emphasis><property>Change...</property></emphasis> button next to + the <emphasis><property>*.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&apos;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>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> Change... </property></emphasis> button next to the <emphasis><property>Location</property></emphasis> field to choose a + location.</para> + + <para><emphasis><property>Context Path</property></emphasis> is the name under which the application will be + deployed.</para> + + <para>The <emphasis><property>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&apos;t have any options + here, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para> + + <para>Finally, <emphasis><property>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&apos;t want to deploy the application, uncheck this + value.</para> + </listitem> + </orderedlist> + + <figure> + <title>The JSF Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war2.png" /> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem> + <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para> + </listitem> + </orderedlist> + </section> + + <section> + <title>Struts</title> + + <orderedlist> + <listitem> + <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select + <emphasis><property>Other > Struts Project From *.war</property></emphasis> from the Import dialog box that + appears.</para> + </listitem> + </orderedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration1.png" /> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the Struts Project From *.war Import Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war2_1.png" /> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem> + <para>Follow the same steps as with the JSF Project From <property>*.war</property> import + wizard.</para> + </listitem> + </orderedlist> + + <figure> + <title>The Struts Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war2_2.png" /> + </imageobject> + </mediaobject> + </figure> + + <orderedlist continuation="continues"> + <listitem> + <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para> + </listitem> + </orderedlist> + <para>The migration process is completed</para> + </section> +</chapter> \ No newline at end of file Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml 2007-11-09 12:09:16 UTC (rev 4821) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -1,182 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="RHDS_migration" xreflabel="RHDS_migration"> - <?dbhtml filename="RHDS_migration.html"?> - <chapterinfo> - <keywordset> - <keyword>Red Hat Developer Studio</keyword> - <keyword>RHDS</keyword> - <keyword>Exadel Studio Pro</keyword> - <keyword>Migration</keyword> - </keywordset> - </chapterinfo> - - <title>Migration of JSF and Struts Projects</title> - <section> - <title>JSF</title> - <para>Red Hat Developer Studio includes an Import <property>JSF Project</property> Wizard that radically simplifies the process of bringing your existing JSF applications - into your Red Hat Developer Studio workspace as JSF projects. You just need to follow these four steps:</para> - <orderedlist> - <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > JSF Project </property></emphasis>from the Import dialog box that appears.</para></listitem> - </orderedlist> - - <figure> - <title>Selecting the Import Menu Item</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration1.png"/> - </imageobject> - </mediaobject> - </figure> - - <figure> - <title>Selecting the Import JSF Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration2.png"/> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem><para>In the first screen of the wizard, select the <emphasis><property>Change...</property></emphasis> button next to the web.xml Location field. Browse to the location of the web.xml file for the application you - want to import as a <property>JSF project</property>. Once you select it, you&apos;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> - </orderedlist> - - <figure> - <title>Selecting the Web.xml File in the The Project Location Screen</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration3.png"/> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para></listitem> - </orderedlist> - <para>On this step Red Hat Developer Studio will try to determine your project - structure and set the values for: <emphasis><property>Web Root</property></emphasis>, <emphasis><property>Source Folder</property></emphasis>, <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>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>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 Red Hat Developer Studio.</para> - <para>First, if the project you are importing is not already a JSF project, select the <emphasis><property>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>Environment</property></emphasis>) and <emphasis><property>Servlet Version</property></emphasis>.</para> - <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para> - <para>The <emphasis><property>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&apos;t have any choices displayed for this, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para> - <para>Finally, <emphasis><property>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&apos;t want to deploy the application, uncheck this value.</para> - - - <figure> - <title>The Project Folders Screen</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration4.png"/> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> - </orderedlist> - - <figure> - <title>Imported Project in the Package Explorer View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration5.png"/> - </imageobject> - </mediaobject> - </figure> - - </section> - <section> - <title>Struts</title> - <orderedlist> - <listitem><para><emphasis><property>Select File > Import...</property></emphasis> from the menu bar, and then select <emphasis><property>Other > Struts Project</property></emphasis> from the Import dialog box that appears.</para></listitem> - </orderedlist> - - <figure> - <title>Selecting the Import Menu Item</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration1.png"/> - </imageobject> - </mediaobject> - </figure> - - <figure> - <title>Selecting the Import Struts Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration2_2.png"/> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem><para>In the Project Location screen of the wizard, select the <emphasis><property>Change... </property></emphasis>button next to the web.xml Location field. Browse the location of the web.xml file for the application you - want to import as a <property>Struts project</property>. Once you select it, you&apos;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> - </orderedlist> - - <figure> - <title>The Project Location Screen</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration2_21.png"/> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem><para>In the next screen, Red Hat 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>Change...</property></emphasis> button.</para></listitem> - </orderedlist> - - <figure> - <title>The Project Modules Screen</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration2_3.png"/> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem><para>In the <emphasis><property>Project Folders</property></emphasis> screen, you can configure the rest of your project. Afterwards click on the <emphasis><property>Finish</property></emphasis> button.</para> - </listitem> - </orderedlist> - <para>On this step Red Hat Developer Studio will try to determine your project structure and set the values for: <emphasis><property>Classes Folder</property></emphasis>, <emphasis><property>Lib Folder</property></emphasis>, and <emphasis><property>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>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 Red Hat Developer Studio.</para> - <para>First, if the project you are importing is not already a Struts project, select the <emphasis><property>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>Environment</property></emphasis> and <emphasis><property>Servlet Version</property></emphasis>.</para> - <para>The <emphasis><property>Context Path</property></emphasis> is the name under which the application will be deployed. </para> - <para>The <emphasis><property>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&apos;t have any choices displayed for this, select<emphasis><property> New...</property></emphasis> to add a new Runtime.</para> - <para>Finally, <emphasis><property>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&apos;t want to deploy the application, uncheck this value.</para> - - - <figure> - <title>The Project Folders Screen</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration2_4.png"/> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> - </orderedlist> - - <figure> - <title>Imported Project in the Package Explorer View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration2_5.png"/> - </imageobject> - </mediaobject> - </figure> - - </section> -</chapter> Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml 2007-11-09 12:09:16 UTC (rev 4821) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_war.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -1,148 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="RHDS_migration_war" xreflabel="RHDS_migration_war"> - <?dbhtml filename="RHDS_migration_war.html"?> - - <chapterinfo> - <keywordset> - <keyword>Red Hat Developer Studio</keyword> - - <keyword>RHDS</keyword> - - <keyword>Exadel Studio Pro</keyword> - </keywordset> - </chapterinfo> - - <title>Migrate JSF and Struts projects from *.war file</title> - - <section> - <title>JSF</title> - - <orderedlist> - <listitem> - <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select - <emphasis><property>Other > JSF Project From *.war</property></emphasis> from the Import dialog box that - appears.</para> - </listitem> - </orderedlist> - - <figure> - <title>Selecting the Import Menu Item</title> - - <mediaobject> - <imageobject> - <imagedata fileref="images/migration1.png" /> - </imageobject> - </mediaobject> - </figure> - - <figure> - <title>Selecting the JSF Project From *.war Import Wizard</title> - - <mediaobject> - <imageobject> - <imagedata fileref="images/migration_war1.png" /> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem> - <para>In the wizard screen, select the <emphasis><property>Change...</property></emphasis> button next to - the <emphasis><property>*.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&apos;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>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> Change... </property></emphasis> button next to the <emphasis><property>Location</property></emphasis> field to choose a - location.</para> - - <para><emphasis><property>Context Path</property></emphasis> is the name under which the application will be - deployed.</para> - - <para>The <emphasis><property>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&apos;t have any options - here, select <emphasis><property>New...</property></emphasis> to add a new Runtime.</para> - - <para>Finally, <emphasis><property>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&apos;t want to deploy the application, uncheck this - value.</para> - </listitem> - </orderedlist> - - <figure> - <title>The JSF Project From *.war Import Wizard</title> - - <mediaobject> - <imageobject> - <imagedata fileref="images/migration_war2.png" /> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem> - <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para> - </listitem> - </orderedlist> - </section> - - <section> - <title>Struts</title> - - <orderedlist> - <listitem> - <para>Select <emphasis><property>File > Import...</property></emphasis> from the menu bar, and then select - <emphasis><property>Other > Struts Project From *.war</property></emphasis> from the Import dialog box that - appears.</para> - </listitem> - </orderedlist> - - <figure> - <title>Selecting the Import Menu Item</title> - - <mediaobject> - <imageobject> - <imagedata fileref="images/migration1.png" /> - </imageobject> - </mediaobject> - </figure> - - <figure> - <title>Selecting the Struts Project From *.war Import Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/migration_war2_1.png" /> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem> - <para>Follow the same steps as with the JSF Project From <property>*.war</property> import - wizard.</para> - </listitem> - </orderedlist> - - <figure> - <title>The Struts Project From *.war Import Wizard</title> - - <mediaobject> - <imageobject> - <imagedata fileref="images/migration_war2_2.png" /> - </imageobject> - </mediaobject> - </figure> - - <orderedlist continuation="continues"> - <listitem> - <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para> - </listitem> - </orderedlist> - <para>The migration process is completed</para> - </section> -</chapter> \ No newline at end of file Deleted: trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml 2007-11-09 12:09:16 UTC (rev 4821) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/migration_ws.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -1,15 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="migration_ws" xreflabel="migration_ws"> - <?dbhtml filename="migration_ws.html"?> - <chapterinfo> - <keywordset> - <keyword>Red Hat Developer Studio</keyword> - <keyword>RHDS</keyword> - <keyword>Exadel Studio Pro</keyword> - </keywordset> - </chapterinfo> - - <title>Migrate workspace</title> - <para>You will not be able to run projects in Red Hat Developer Studio - using <property>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>Red Hat Developer Studio workspace</property> and make an import as it is described in the following chapters.</para> -</chapter> Added: trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml =================================================================== --- trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml (rev 0) +++ trunk/documentation/guides/userguide/Exadel-migration/en/modules/workspace.xml 2007-11-09 13:47:25 UTC (rev 4822) @@ -0,0 +1,15 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="workspace" xreflabel="workspace"> + <?dbhtml filename="workspace.html"?> + <chapterinfo> + <keywordset> + <keyword>Red Hat Developer Studio</keyword> + <keyword>RHDS</keyword> + <keyword>Exadel Studio Pro</keyword> + </keywordset> + </chapterinfo> + + <title>Migrate workspace</title> + <para>You will not be able to run projects in Red Hat Developer Studio + using <property>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>Red Hat Developer Studio workspace</property> and make an import as it is described in the following chapters.</para> +</chapter>