[jbosstools-commits] JBoss Tools SVN: r20770 - in branches/jbosstools-3.1.x/documentation/guides/Exadel-migration: en-US and 3 other directories.

Author: irooskov(a)redhat.com Date: 2010-03-11 18:39:53 -0500 (Thu, 11 Mar 2010) New Revision: 20770 Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Author_Group.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Book_Info.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.ent branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Preface.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Revision_History.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/favicon0.ico branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_1.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_10.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_2.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_3.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_4.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_5.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_6.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_7.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_8.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_9.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_1.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_2.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_3.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_4.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_5.png branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/introduction.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts_war.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master_output.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/workspace.xml branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/publican.cfg Removed: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en/ Modified: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/pom.xml Log: modified to build with publican and maven Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Author_Group.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Author_Group.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Author_Group.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup><author><firstname>JBoss Tools Team</firstname></author></authorgroup> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Book_Info.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Book_Info.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<bookinfo><title>Exadel Studio Migration Guide</title><subtitle>Provides information about migration to the JBoss Developer Studio.</subtitle><productname>JBoss Developer Studio</productname><productnumber>3.0</productnumber><edition>1.0</edition><pubsnumber>0</pubsnumber><abstract><para>The Exadel Studio Migration Guide explains how to migrate from Exadel Studio to the JBoss Developer Studio.</para></abstract><corpauthor><inlinemediaobject><imageobject><imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata></imageobject></inlinemediaobject></corpauthor><xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g... href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g... Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.ent =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.ent (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.ent 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,4 @@ +<!ENTITY PRODUCT "JBoss"> +<!ENTITY BOOKID "Exadel_Studio_Migration_Guide"> +<!ENTITY YEAR "2010"> +<!ENTITY HOLDER "Red Hat"> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Exadel_Studio_Migration_Guide.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,12 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<book> +<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="workspace.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="jsf_struts.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="jsf_struts_war.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +</book> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Preface.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Preface.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<preface><title>Preface</title><xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g... href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include&g... Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Revision_History.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Revision_History.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/Revision_History.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,4 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<appendix><title>Revision History</title><simpara><revhistory><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov@redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/favicon0.ico =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/favicon0.ico ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_1.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_10.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_10.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_2.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_3.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_4.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_5.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_6.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_6.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_7.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_7.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_8.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_8.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_9.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts/migration_9.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_1.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_2.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_3.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_3.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_4.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_4.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_5.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/images/jsf_struts_war/migration_war_5.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/introduction.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/introduction.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/introduction.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,70 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="introduction" 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>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.4.x by the standard Eclipse means.</para> + + <section> + <title>Key Features of Projects Migration to JBoss Developer Studio</title> + <para>For a start, we propose you to look through the table of main features of migrating projects to JBoss Developer Studio:</para> + + <table> + + <title>Key Features of Project Migration to JBoss Developer Studio</title> + <tgroup cols="3"> + + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <colspec colnum="3" align="left" colwidth="2*"/> + + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> + + <tbody> + + <row> + <entry><para>Import JSF Project Wizard</para></entry> + <entry><para>It simplifies the process of bringing your existing JSF applications into your JBoss Developer Studio workspace as JSF projects. The import is possible with *.war files.</para></entry> + <entry> + <link linkend="import_jsf">Migration of JSF project</link> and <link linkend="jsf_war">Migration of JSF project from *.war file</link> + </entry> + </row> + + <row> + <entry><para>Import Struts Project Wizard</para></entry> + <entry><para>It simplifies the process of bringing your existing Struts applications into your JBoss Developer Studio workspace as Struts projects. The import is possible with *.war files.</para></entry> + <entry> + <link linkend="struts_import">Migration of Struts project</link> and <link linkend="struts_war">Migration of Struts project from *.war file</link> + </entry> + </row> + + </tbody> + + </tgroup> + </table> + + </section> + + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/too... in the corresponding release directory.</para> + <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">htt... + + </section> + +</chapter> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,183 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="jsf_struts" 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>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>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> + </itemizedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_1.png"/> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the Import JSF Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_2.png"/> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>In the first screen of the wizard, select the <emphasis><property>Change...</property></emphasis> button next to the <emphasis><property>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>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> + </itemizedlist> + + <figure> + <title>Selecting the Web.xml File in the Project Location Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_3.png"/> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist id="import_jsf_screen"> + <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> + </itemizedlist> + <para>On this step JBoss 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 JBoss 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/migration_4.png"/> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> + </itemizedlist> + + <figure> + <title>Imported Project in the Package Explorer View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_5.png"/> + </imageobject> + </mediaobject> + </figure> + + </section> + <section id="struts_import"> + <title>Struts</title> + <itemizedlist> + <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> + </itemizedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_1.png"/> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the Import Struts Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_6.png"/> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>In the Project Location screen of the wizard, select the <emphasis><property>Change... </property></emphasis>button next to the <emphasis><property>web.xml Location</property></emphasis> 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> + </itemizedlist> + + <figure> + <title>The Project Location Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_10.png"/> + </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>Change...</property></emphasis> button.</para></listitem> + </itemizedlist> + + <figure> + <title>The Project Modules Screen</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_7.png"/> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <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> + </itemizedlist> + <para>On this step JBoss 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 JBoss 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/migration_8.png"/> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>Once the project is imported, it will appear in the Package Explorer view.</para></listitem> + </itemizedlist> + + <figure> + <title>Imported Project in the Package Explorer View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts/migration_9.png"/> + </imageobject> + </mediaobject> + </figure> + + </section> +</chapter> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts_war.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts_war.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/jsf_struts_war.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,157 @@ +<?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>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 id="jsf_war"> + <title>JSF</title> + + <itemizedlist> + <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> + </itemizedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_1.png" /> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the JSF Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_2.png" /> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <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> + </itemizedlist> + + <figure> + <title>The JSF Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_3.png" /> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para> + </listitem> + </itemizedlist> + </section> + + <section id="struts_war"> + <title>Struts</title> + + <itemizedlist> + <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> + </itemizedlist> + + <figure> + <title>Selecting the Import Menu Item</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_1.png" /> + </imageobject> + </mediaobject> + </figure> + + <figure> + <title>Selecting the Struts Project From *.war Import Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_4.png" /> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>Follow the same steps as with the JSF Project From <property>*.war</property> import + wizard.</para> + </listitem> + </itemizedlist> + + <figure> + <title>The Struts Project From *.war Import Wizard</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_struts_war/migration_war_5.png" /> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para>Click on the <emphasis><property>Finish</property></emphasis> button.</para> + </listitem> + </itemizedlist> + <para>The migration process is completed</para> + + <para>If there&apos;s anything we didn&apos;t cover or you can&apos;t figure + out, please feel free to visit our <ulink + url="http://www.jboss.com/index.html?module=bb&amp;op=viewforum&... + >JBoss Developer Studio Users Forum</ulink> or <ulink + url="http://www.jboss.com/index.html?module=bb&amp;op=viewforum&... + >JBoss Tools Users Forum</ulink> to ask questions. There we are also looking for + your suggestions and comments.</para> + </section> + +</chapter> \ No newline at end of file Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,58 @@ +<?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 "jsf_struts.xml"> +<!ENTITY jsf_struts_war SYSTEM "jsf_struts_war.xml"> +<!ENTITY introduction SYSTEM "introduction.xml"> +<!ENTITY workspace SYSTEM "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> + <bookinfo> + <title>Exadel Studio Migration Guide</title> + + + <copyright> + <year>2007</year> + <year>2008</year> + <year>2009</year> + <year>2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo> +Version: 3.0.0.GA +</releaseinfo> + +<abstract> + <title/> + <para> + <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/Exadel-mig... version</ulink> + </para> +</abstract> + + + </bookinfo> + + <toc/> +&introduction; +&workspace; +&jsf_struts; +&jsf_struts_war; + + +</book> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master_output.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master_output.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/master_output.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,479 @@ +<?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> + + + <copyright> + <year>2007</year> + <year>2008</year> + <year>2009</year> + <year>2010</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo> +Version: 3.0.0.GA +</releaseinfo> + +<abstract> + <title></title> + <para> + <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/Exadel-mig... version</ulink> + </para> +</abstract> + + + </bookinfo> + + <toc></toc> + +<chapter id="introduction" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/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.4.x by the standard Eclipse means.</para> + + <section> + <title>Key Features of Projects Migration to JBoss Developer Studio</title> + <para>For a start, we propose you to look through the table of main features of migrating projects to JBoss Developer Studio:</para> + + <table> + + <title>Key Features of Project Migration to JBoss Developer Studio</title> + <tgroup cols="3"> + + <colspec align="left" colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="4*"></colspec> + <colspec align="left" colnum="3" colwidth="2*"></colspec> + + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> + + <tbody> + + <row> + <entry><para>Import JSF Project Wizard</para></entry> + <entry><para>It simplifies the process of bringing your existing JSF applications into your JBoss Developer Studio workspace as JSF projects. The import is possible with *.war files.</para></entry> + <entry> + <link linkend="import_jsf">Migration of JSF project</link> and <link linkend="jsf_war">Migration of JSF project from *.war file</link> + </entry> + </row> + + <row> + <entry><para>Import Struts Project Wizard</para></entry> + <entry><para>It simplifies the process of bringing your existing Struts applications into your JBoss Developer Studio workspace as Struts projects. The import is possible with *.war files.</para></entry> + <entry> + <link linkend="struts_import">Migration of Struts project</link> and <link linkend="struts_war">Migration of Struts project from *.war file</link> + </entry> + </row> + + </tbody> + + </tgroup> + </table> + + </section> + + <section> + <title>Other relevant resources on the topic</title> + <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/too... in the corresponding release directory.</para> + <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">htt... + + </section> + +</chapter> + + +<chapter id="workspace" xml:base="file:///home/vchukhutsina/repos/ochik_jboss/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/vchukhutsina/repos/ochik_jboss/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 id="struts_import"> + <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/vchukhutsina/repos/ochik_jboss/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 id="jsf_war"> + <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 id="struts_war"> + <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> + + <para>If there's anything we didn't cover or you can't figure + out, please feel free to visit our + <ulink url="http://www.jboss.com/index.html?module=bb&amp;op=viewforum&... + JBoss Developer Studio Users Forum</ulink> or + <ulink url="http://www.jboss.com/index.html?module=bb&amp;op=viewforum&... Tools Users Forum</ulink> to ask questions. There we are also looking for + your suggestions and comments.</para> + </section> + +</chapter> + + +</book> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/workspace.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/workspace.xml (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/en-US/workspace.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,15 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="workspace" 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>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>JBoss Developer Studio workspace</property> and make an import as it is described in the following chapters.</para> +</chapter> Modified: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/pom.xml =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/pom.xml 2010-03-11 18:01:41 UTC (rev 20769) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/pom.xml 2010-03-11 23:39:53 UTC (rev 20770) @@ -32,7 +32,7 @@ <profile> <id>releaseJBDS</id> <properties> - <master>master.xml</master> + <master>master_output.xml</master> <xsl-single>classpath:/xslt/com/jboss/tools/xhtml-single-release.xsl</xsl-single> <xsl-chunked>classpath:/xslt/com/jboss/tools/xhtml-release.xsl</xsl-chunked> <xsl-pdf>classpath:/xslt/com/jboss/tools/pdf.xsl</xsl-pdf> @@ -89,9 +89,9 @@ </dependencies> <configuration> <sourceDocumentName>${master}</sourceDocumentName> - <sourceDirectory>${pom.basedir}/en</sourceDirectory> + <sourceDirectory>${pom.basedir}/en-US</sourceDirectory> <imageResource> - <directory>${pom.basedir}/en</directory> + <directory>${pom.basedir}/en-US</directory> <includes> <include>images/**/*</include> </includes> Added: branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/publican.cfg =================================================================== --- branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/publican.cfg (rev 0) +++ branches/jbosstools-3.1.x/documentation/guides/Exadel-migration/publican.cfg 2010-03-11 23:39:53 UTC (rev 20770) @@ -0,0 +1,7 @@ +# Config::Simple 4.59 +# Fri Nov 20 13:19:45 2009 + +xml_lang: en-US +type: Book +brand: JBoss +