Migrating from XCode to WOLips

As you know, if you plan to continue using WebObjects since Apple deprecated EOModeler, WebObjects Builder and RuleModeler.  So, what's the steps to migrate ?

• First, install Eclipse (3.2.x series)

• After installating Eclipse, start it and follow the instructions from this wiki.

• WOLips is installed ?  You can start migrating.

• You have three choices for migrations for projects.  You can do a manual migration, you can use a Java tool written by Pascal Robert or you can use the "fleeto" script from Chuck Hill over at Global Village.
  • If you are using Pascal's tool, please note that it does the following :
    • It use a XML configuration file, and you can convert multiple projects at the same time
    • It parse the original Xcode project by creating a readable plist with /Developer/Tools/pbprojectdump
    • It create a new WOLips project for each Xcode project listed in the XML configuration file
    • It finds all files to copy from the Xcode and copy them to the newly created WOLips project
      • Java files (.java) are copied to the Sources folder
      • Components (.wo) and API (.api) files are copied to the Components folder
      • Files ending with "Properties" are copied to the Resources folder
      • EOModels (.eomodeld) are copied to the Resources folder
      • Properties files (.prop and .properties) are copied to the Resources folder
      • ReportMill reports (.rpt) are copied to the Resources folder
      • Java libs (.jar) are copied to the Librairies folder
      • Direct2Web rules (.d2wmodel) are copied to the Resources folder
      • EOGenerator templates (.eotemplate) are copied to the Resources folder
      • All other files are copied into the WebServerResources folder
    • If MacRoman encoding is found for a file, it will the convert the file to UTF-8
    • Have a look at the Readme file included with the tool to find out how to use it
  • If you are using Chuck's script, please note that it does the following :
    • Checks to see if you actually created a project with a Wonder layout in Eclipse (the script looks for a .project file)
    • Checks to see if the current folder (the original XCode project) has a .xcodeproj file
    • Does a find of all .java files in the XCode project folder and copies them over to the "Sources" folder of the Eclipse project
    • Copies all .wo and .api files found in the root folder of the XCode folder into the "Components" folder of the Eclipse project
    • Copies all .eomodeld, .plist, .txt, .html, .xml and the Properties files found in the root folder of the XCode folder into the "Resources" folder of the Eclipse project
    • Copies all .gif, .jpeg, .js, .css and .map files found in the root folder of the XCode folder into the "WebServerResources" folder of the Eclipse project
  • So if you have files (for examples, your .wo files were in a WOComponents folder), you either have to modify the script or move the files by hand
  • You didn't use Chuck's script ?  Check out this page.

• Go back to Eclipse, right-click and hit "Refresh". You should see your files in the various folders, and Eclipse will automatically build your project. After that, you just need to check for any errors and warnings and fix them.
  • In our case, we had old EOModels that where using NSdoubleNumber instead of NSNumber. BUT Entity Modeler won't show those errors inside Eclipse, instead you will see blank stuff. You see the actual errors in Console.app instead, so be sure to check that log if you have any strange errors.