Table of Contents 
Previous Section
Converting Old Projects
Under version 3.5 of WebObjects, projects are organized differently than under previous versions. This section describes how to convert your old projects to the new organization so that you can work with them in WebObjects 3.5 and beyond. Performing the Conversion
To convert your project, open it in Project Builder. (It's a good idea to create a backup of your project before converting.) If your project was created prior to WebObjects 3.5, Project Builder detects that a conversion needs to be done. It reassigns the files in your project to new suitcases, as appropriate. It uses the file extension to determine what action to take; if there are files whose extensions it doesn't recognize, it reports these at the end of the conversion, and you must manually assign those files to the appropriate suitcases.
- Components (with a .wo extension) are added to the Web Components suitcase. Note: Only components found in the top level of the project and each subproject are moved automatically.
- Java code (.java) files are moved from the components into the Classes suitcase and stored at the top level of the project on disk. Note: Keep in mind that this may affect your source/revision control system.
- Resources (previously in the Other Resources suitcase) are put into two new suitcases. Images with known extensions are assigned to the Web Server Resources suitcase. Other resources are assigned to the Resources suitcase. Files with unrecognized extensions are left out and you are notified.
- WOProject.plist is no longer used and is deleted if it is in the project.
- Several new makefile variables have been added and are appended to your existing Makefile.preamble with default values assigned.
- All existing subprojects are recursively converted in the same manner as the top-level project.
In addition, you are asked if you want to add two optional subprojects (ClientSideJava and CommonJava) to your project. You can use these to divide your Java code into client-side, server-side or common Java. See "Subprojects" for more information.
Once the conversion has begun, there is no way to cancel it. If you choose not to convert at all, you may not be able to view some of your files, since they are assigned to suitcases that aren't visible.
Moving Your Images
After the project is converted, there are additional changes you may want to make in order to take advantage of the new features of WebObjects 3.5. In previous versions, images were stored inside the components themselves. To support the new "split installation" procedure, images should be stored in the Web Server Resources suitcase, so that the web server can access them at run time. (When you build your project, the items in this suitcase are copied to the WebServerResources directory inside the application wrapper.)When using the dynamic elements WOImage and WOActiveImage, you use their filename attribute to reference images inside the WebServerResources directory. You may also have images in a framework that can be shared by multiple applications. To access these images, use the framework attribute to specify the framework name. See "Working With Dynamic Elements" in this document and the Dynamic Elements Reference for more information.