Exadel Studio Migration Guide

From jbosstools-commits at lists.jboss.org Wed Feb 17 13:57:29 2010 Content-Type: multipart/mixed; boundary="===============0980229237188655701==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r20329 - trunk/documentation/guides/Exadel-migration/en. Date: Wed, 17 Feb 2010 13:57:29 -0500 Message-ID: <201002171857.o1HIvTfr007356@svn01.web.mwc.hst.phx2.redhat.com> --===============0980229237188655701== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ochikvina Date: 2010-02-17 13:57:28 -0500 (Wed, 17 Feb 2010) New Revision: 20329 Modified: trunk/documentation/guides/Exadel-migration/en/master_output.xml Log:

https://jira.jboss.org/jira/browse/JBDS-1104 - Updated versions,correcte= d master_output file

Modified: trunk/documentation/guides/Exadel-migration/en/master_output.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/documentation/guides/Exadel-migration/en/master_output.xml 2010-0= 2-17 18:48:36 UTC (rev 20328) +++ trunk/documentation/guides/Exadel-migration/en/master_output.xml 2010-0= 2-17 18:57:28 UTC (rev 20329) @@ -20,455 +20,461 @@ = = = = -]> - - Exadel Studio Migration Guide - = - April 2008 - - 2007 - 2009 - JBoss by Red Hat - - -Version: 3.1.0.CR1 - - - - - - PDF version - - - - - = - - = - - - - - - JBoss Developer Studio - JBDS - Exadel Studio Pro - - - - Introduction - This document is intended to help you to migrate an existing Exadel= JSF or Struts projects - into JBoss Developer Studio. Pref= erences 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 m= eans. - = -

- Key Features of Projects Migration to JBoss Developer Studio</tit= le> - <para>For a start, we propose you to look through the table of main feat= ures of migrating projects to JBoss Developer Studio:</para> - = - <table> - = - <title>Key Features of Project Migration to JBoss Developer Studio</tit= le> - <tgroup cols=3D"3"> - = - <colspec align=3D"left" colnum=3D"1" colwidth=3D"2*"></colspec> - <colspec colnum=3D"2" colwidth=3D"4*"></colspec> - <colspec align=3D"left" colnum=3D"3" colwidth=3D"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. T= he import is possible with *.war files.</para></entry> - <entry> - <link linkend=3D"import_jsf">Migration of JSF project</link> and <l= ink linkend=3D"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 Str= uts applications into your JBoss Developer Studio workspace as Struts proje= cts. The import is possible with *.war files.</para></entry> - <entry> - <link linkend=3D"struts_import">Migration of Struts project</link> = and <link linkend=3D"struts_war">Migration of Struts project from *.war fil= e</link> - </entry> - </row> - = - </tbody> - = - </tgroup> - </table> - = - </section> - = - <section> - <title>Other relevant resources on the topic - All JBoss Developer Studio/JBoss Tools release documentation you c= an find athttp://docs.jboss.org= /tools in the corresponding release directory. - The latest documentation builds are available at http://download.jboss.org/= jbosstools/nightly-docs. - -

- - - - - - - - - JBoss Developer Studio - JBDS - Exadel Studio Pro - - - = - Migrate workspace - You will not be able to run projects in JBoss Developer Studio - using Exadel Studio workspace. In= this case, project capabilities and settings specified in Exadel Studio wi= ll be lost. The simplest way to avoid this, is to copy your projects in JBoss Developer Studio workspace and ma= ke an import as it is described in the following chapters. - - - - - - - - JBoss Developer Studio - JBDS - Exadel Studio Pro - Migration - - - = - Migration of JSF and Struts Projects - In this chapter you can find concise description of migration of JS= F and Struts Projects. -

= - JSF - JBoss Developer Studio includes an Import JSF Project Wizard that radically simplifies the process of = bringing your existing JSF applications - into your JBoss Developer Studio workspace as JSF projects. You just ne= ed to follow these four steps: - - Select File > = Import... from the menu bar, and then select Other > JSF Project = from the Import dialog box that appears. - - = -

- Selecting the Import Menu Item - = - - - - - - = -

- Selecting the Import JSF Project Wizard - = - - - - - - = - - In the first screen of the wizard, select the Change... button next to= the web.xml Location field. Browse to the location of the web.xml file for the applicatio= n 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 web.xml file you selected. = - You can edit this project name, if you wish. - - = -

- Selecting the Web.xml File in the Project Location Screen - = - - - - - - = - - In the Project Fo= lders screen, you can configure the rest of your proj= ect. Afterwards click on the Finish button. - - On this step JBoss Developer Studio will try to determine your pro= ject - structure and set the values for: Web Root, Sour= ce Folder, Clas= ses Folder, Lib= Folder. 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 clickin= g the Change...= button. - After dealing with these settings, you have to work through a fe= w more configuration settings. These settings deal primarily with how the p= roject will be deployed within JBoss Developer Studio. - First, if the project you are importing is not already a JSF proje= ct, select the Add Libraries check box to add all the JSF-related libraries to your projec= t. - Then, you may select the JavaServer Faces implementation (Environment) and Servlet Version. - The Context Path<= /emphasis> is the name under which the application will be deployed. - The Runtime 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 s= electing a Runtime. If you don't have any choices displayed for this, selec= t New... to add= a new Runtime. - Finally, Target Server sets the server to deploy the application under. The Targe= t Server corresponds to the Runtime value selected above. If you don't want= to deploy the application, uncheck this value. - = - = -

- The Project Folders Screen - = - - - - - - = - - Once the project is imported, it will appear in the Pac= kage Explorer view. - - = -

- Imported Project in the Package Explorer View - = - - - - - - = -

- Struts - - Select File > = Import... from the menu bar, and then select Other > Struts Project from the Import dialog box that appears. - - = -

- Selecting the Import Menu Item - = - - - - - - = -

- Selecting the Import Struts Project Wizard - = - - - - - - = - - In the Project Location screen of the wizard, select th= e Change... but= ton next to the web.xml Location field. Browse the location of the web.xml file for the ap= plication you = - want to import as a Struts project. Once you select it, you'll be returned to the dialog box to see a proj= ect name derived from the web.xml file you selected. = - You can edit this project name, if you wish. - - = -

- The Project Location Screen - = - - - - - - = - - 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 Change... button. - - = -

- The Project Modules Screen - = - - - - - - = - - In the Project Fo= lders screen, you can configure the rest of your proj= ect. Afterwards click on the Finish button. - - - On this step JBoss Developer Studio will try to determine your pro= ject structure and set the values for: Classes Folder, Lib Folder, and Ant Build File. If your project has a custom stru= cture, some values might not be set. If this is the case, you can manually = set those values by clicking Change. - After dealing with these settings, you have to work through a fe= w more configuration settings. These settings deal primarily with how the p= roject will be deployed within JBoss Developer Studio. - First, if the project you are importing is not already a Struts pr= oject, select the Add Libraries check box to add all the Struts-related libraries to your = project. - Then, you may select the Struts Environment and Servlet Version. - The Context Path<= /emphasis> is the name under which the application will be deployed. - The Runtime 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 s= electing a Runtime. If you don't have any choices displayed for this, selec= t New... to add= a new Runtime. - Finally, Target Server sets the server to deploy the application under. The Targe= t Server corresponds to the Runtime value selected above. If you don't want= to deploy the application, uncheck this value. - - = -

- The Project Folders Screen - = - - - - - - = - - Once the project is imported, it will appear in the Pac= kage Explorer view. - - = -

- Imported Project in the Package Explorer View - = - - - - - - -

- - - - - - - - - JBoss Developer Studio - - JBDS - - Exadel Studio Pro - - - - Migrate JSF and Struts projects from *.war file - After you familiarized oneself with last chapter you can read this= chapter. It looks as if you read in last chapter. -

- JSF - - - - Select File > Impor= t... from the menu bar, and then select - Other > JSF Project From = *.war from the Import dialog box that - appears. - - - -

- Selecting the Import Menu Item - - - - - - - - -

- Selecting the JSF Project From *.war Import Wizard - - - - - - - - - - - In the wizard screen, select the Change... button next to - the *.war Location field. Browse to the location of the *.war file for - the application you want to import as a JSF project. Once you sele= ct - 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. - - Uncheck the Use Defaul= t Path check box if you want to import - your project outside of the Eclipse workspace. In this case, you w= ould - use Change... button next to the Location= field to choose a - location. - - Context Path is the name under which the application will be - deployed. - - The Runtime= 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 New... to add a new Runtime. - - Finally, Target Server= 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. - - - -

- The JSF Project From *.war Import Wizard - - - - - - - - - - - Click on the Finish button. - - -

- -

- Struts - - - - Select File > Impor= t... from the menu bar, and then select - Other > Struts Project Fr= om *.war from the Import dialog box that - appears. - - - -

- Selecting the Import Menu Item - - - - - - - - -

- Selecting the Struts Project From *.war Import Wizard - - - - - - - - - - Follow the same steps as with the JSF Project From *.war import - wizard. - - - -

- The Struts Project From *.war Import Wizard - - - - - - - - - - - Click on the Finish button. - - - The migration process is completed - = - If there's anything we didn't cover or you can't figure - out, please feel free to visit our JBoss Developer St= udio Users Forum or JBoss Tools Users Forum = to ask questions. There we are also looking for - your suggestions and comments. -

- = - = - - = - +]> + + Exadel Studio Migration Guide + = + = + + 2007 + 2008 + 2009 + 2010 + JBoss by Red Hat + + +Version: 3.0.0.GA + + + + + + PDF version + + + + + = + + = + + + + + + JBoss Developer Studio + JBDS + Exadel Studio Pro + + + + Introduction + This document is intended to help you to migrate an existing Exadel= JSF or Struts projects + into JBoss Developer Studio. Pref= erences 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 m= eans. + = +

+ Key Features of Projects Migration to JBoss Developer Studio</tit= le> + <para>For a start, we propose you to look through the table of main feat= ures of migrating projects to JBoss Developer Studio:</para> + = + <table> + = + <title>Key Features of Project Migration to JBoss Developer Studio</tit= le> + <tgroup cols=3D"3"> + = + <colspec align=3D"left" colnum=3D"1" colwidth=3D"2*"></colspec> + <colspec colnum=3D"2" colwidth=3D"4*"></colspec> + <colspec align=3D"left" colnum=3D"3" colwidth=3D"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. T= he import is possible with *.war files.</para></entry> + <entry> + <link linkend=3D"import_jsf">Migration of JSF project</link> and <l= ink linkend=3D"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 Str= uts applications into your JBoss Developer Studio workspace as Struts proje= cts. The import is possible with *.war files.</para></entry> + <entry> + <link linkend=3D"struts_import">Migration of Struts project</link> = and <link linkend=3D"struts_war">Migration of Struts project from *.war fil= e</link> + </entry> + </row> + = + </tbody> + = + </tgroup> + </table> + = + </section> + = + <section> + <title>Other relevant resources on the topic + All JBoss Developer Studio/JBoss Tools release documentation you c= an find athttp://docs.jboss.org= /tools in the corresponding release directory. + The latest documentation builds are available at http://download.jboss.org/= jbosstools/nightly-docs. + +

+ + + + + + + + + JBoss Developer Studio + JBDS + Exadel Studio Pro + + + = + Migrate workspace + You will not be able to run projects in JBoss Developer Studio + using Exadel Studio workspace. In= this case, project capabilities and settings specified in Exadel Studio wi= ll be lost. The simplest way to avoid this, is to copy your projects in JBoss Developer Studio workspace and ma= ke an import as it is described in the following chapters. + + + + + + + + JBoss Developer Studio + JBDS + Exadel Studio Pro + Migration + + + = + Migration of JSF and Struts Projects + In this chapter you can find concise description of migration of JS= F and Struts Projects. +

= + JSF + JBoss Developer Studio includes an Import JSF Project Wizard that radically simplifies the process of = bringing your existing JSF applications + into your JBoss Developer Studio workspace as JSF projects. You just ne= ed to follow these four steps: + + Select File > = Import... from the menu bar, and then select Other > JSF Project = from the Import dialog box that appears. + + = +

+ Selecting the Import Menu Item + = + + + + + + = +

+ Selecting the Import JSF Project Wizard + = + + + + + + = + + In the first screen of the wizard, select the Change... button next to= the web.xml Location field. Browse to the location of the web.xml file for the applicatio= n 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 web.xml file you selected. = + You can edit this project name, if you wish. + + = +

+ Selecting the Web.xml File in the Project Location Screen + = + + + + + + = + + In the Project Fo= lders screen, you can configure the rest of your proj= ect. Afterwards click on the Finish button. + + On this step JBoss Developer Studio will try to determine your pro= ject + structure and set the values for: Web Root, Sour= ce Folder, Clas= ses Folder, Lib= Folder. 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 clickin= g the Change...= button. + After dealing with these settings, you have to work through a fe= w more configuration settings. These settings deal primarily with how the p= roject will be deployed within JBoss Developer Studio. + First, if the project you are importing is not already a JSF proje= ct, select the Add Libraries check box to add all the JSF-related libraries to your projec= t. + Then, you may select the JavaServer Faces implementation (Environment) and Servlet Version. + The Context Path<= /emphasis> is the name under which the application will be deployed. + The Runtime 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 s= electing a Runtime. If you don't have any choices displayed for this, selec= t New... to add= a new Runtime. + Finally, Target Server sets the server to deploy the application under. The Targe= t Server corresponds to the Runtime value selected above. If you don't want= to deploy the application, uncheck this value. + = + = +

+ The Project Folders Screen + = + + + + + + = + + Once the project is imported, it will appear in the Pac= kage Explorer view. + + = +

+ Imported Project in the Package Explorer View + = + + + + + + = +

+ Struts + + Select File > = Import... from the menu bar, and then select Other > Struts Project from the Import dialog box that appears. + + = +

+ Selecting the Import Menu Item + = + + + + + + = +

+ Selecting the Import Struts Project Wizard + = + + + + + + = + + In the Project Location screen of the wizard, select th= e Change... but= ton next to the web.xml Location field. Browse the location of the web.xml file for the ap= plication you = + want to import as a Struts project. Once you select it, you'll be returned to the dialog box to see a proj= ect name derived from the web.xml file you selected. = + You can edit this project name, if you wish. + + = +

+ The Project Location Screen + = + + + + + + = + + 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 Change... button. + + = +

+ The Project Modules Screen + = + + + + + + = + + In the Project Fo= lders screen, you can configure the rest of your proj= ect. Afterwards click on the Finish button. + + + On this step JBoss Developer Studio will try to determine your pro= ject structure and set the values for: Classes Folder, Lib Folder, and Ant Build File. If your project has a custom stru= cture, some values might not be set. If this is the case, you can manually = set those values by clicking Change. + After dealing with these settings, you have to work through a fe= w more configuration settings. These settings deal primarily with how the p= roject will be deployed within JBoss Developer Studio. + First, if the project you are importing is not already a Struts pr= oject, select the Add Libraries check box to add all the Struts-related libraries to your = project. + Then, you may select the Struts Environment and Servlet Version. + The Context Path<= /emphasis> is the name under which the application will be deployed. + The Runtime 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 s= electing a Runtime. If you don't have any choices displayed for this, selec= t New... to add= a new Runtime. + Finally, Target Server sets the server to deploy the application under. The Targe= t Server corresponds to the Runtime value selected above. If you don't want= to deploy the application, uncheck this value. + + = +

+ The Project Folders Screen + = + + + + + + = + + Once the project is imported, it will appear in the Pac= kage Explorer view. + + = +

+ Imported Project in the Package Explorer View + = + + + + + + +

+ + + + + + + + + JBoss Developer Studio + + JBDS + + Exadel Studio Pro + + + + Migrate JSF and Struts projects from *.war file + After you familiarized oneself with last chapter you can read this= chapter. It looks as if you read in last chapter. +

+ JSF + + + + Select File > Impor= t... from the menu bar, and then select + Other > JSF Project From = *.war from the Import dialog box that + appears. + + + +

+ Selecting the Import Menu Item + + + + + + + + +

+ Selecting the JSF Project From *.war Import Wizard + + + + + + + + + + + In the wizard screen, select the Change... button next to + the *.war Location field. Browse to the location of the *.war file for + the application you want to import as a JSF project. Once you sele= ct + 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. + + Uncheck the Use Defaul= t Path check box if you want to import + your project outside of the Eclipse workspace. In this case, you w= ould + use Change... button next to the Location= field to choose a + location. + + Context Path is the name under which the application will be + deployed. + + The Runtime= 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 New... to add a new Runtime. + + Finally, Target Server= 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. + + + +

+ The JSF Project From *.war Import Wizard + + + + + + + + + + + Click on the Finish button. + + +

+ +

+ Struts + + + + Select File > Impor= t... from the menu bar, and then select + Other > Struts Project Fr= om *.war from the Import dialog box that + appears. + + + +

+ Selecting the Import Menu Item + + + + + + + + +

+ Selecting the Struts Project From *.war Import Wizard + + + + + + + + + + Follow the same steps as with the JSF Project From *.war import + wizard. + + + +

+ The Struts Project From *.war Import Wizard + + + + + + + + + + + Click on the Finish button. + + + The migration process is completed + = + If there's anything we didn't cover or you can't f= igure + out, please feel free to visit our JBoss Developer Studio Users Forum or JBoss Tools Users Forum to ask questions. There we are also= looking for + your suggestions and comments. +

+ = + = + + = + --===============0980229237188655701==--