From jbosstools-commits at lists.jboss.org Thu Jan 29 12:32:36 2009 Content-Type: multipart/mixed; boundary="===============0654817250179138253==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r13333 - branches/jbosstools-3.0.0.CR2/documentation/guides/Exadel-migration/en. Date: Thu, 29 Jan 2009 12:32:35 -0500 Message-ID: --===============0654817250179138253== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: ochikvina Date: 2009-01-29 12:32:35 -0500 (Thu, 29 Jan 2009) New Revision: 13333 Added: branches/jbosstools-3.0.0.CR2/documentation/guides/Exadel-migration/en/m= aster_output.xml Log: https://jira.jboss.org/jira/browse/JBDS-571- adding the master_output.xml; Added: branches/jbosstools-3.0.0.CR2/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 --- branches/jbosstools-3.0.0.CR2/documentation/guides/Exadel-migration/en/= master_output.xml (rev 0) +++ branches/jbosstools-3.0.0.CR2/documentation/guides/Exadel-migration/en/= master_output.xml 2009-01-29 17:32:35 UTC (rev 13333) @@ -0,0 +1,422 @@ + + + + + + + + + + + + + + + + + = + = = + +]> + + Exadel Studio Migration Guide + = + April 2008 + + 2007 + 2008 + JBoss, a division of Red Hat Inc. + + +Version: 2.0.0.CR2 + + + + + + PDF version + + + + + = + + = + + + + + + JBoss Developer Studio + JBDS + Exadel Studio Pro + + + = + Introduction + This document is intended to help you to migrate an existing Exad= el JSF or Struts projects = + into JBoss Developer Studio. Pr= eferences 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. + +
+ Other relevant resources on the topic + All JBoss Developer Studio/JBoss Tools documentation you can find <= ulink url=3D"http://docs.jboss.org/tools">here. + The latest documentation builds are available here. + = +
+ + + + + + + + + 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 +
+ = + + = + --===============0654817250179138253==--