Child pages
  • Project Wonder Installation on Windows

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Once the WOlips plugin is installed, you will need to install the core frameworks with the help of WOInstaller.jar, available from the wocommunity.org site. After, open a Command Prompt, and enter the following command:

Code Block

java -jar \path\to\WOInstaller.jar 5.4.3 c:\Apple

You might get an error about a missing folder in C:\Apple\Library, you can ignore this error.

NOTE: Above WOInstaller.jar was built in 2008. Inside the jar file, the path statement for the dmg file is incorrect. Apple has moved this file. This jar file WOInstaller2013_08_10.jar has been updated for the correct path. Only tested on WinXP system. Don't know about other versions.

Step 4:  Link the Framework to WOlips through the properties configuration file

...

Note

You must replace <YOUR_USER_NAME_HERE!> with your the username which installed the framework.

Code Block

wo.system.root=/Developer/Versions/WebObjects543/System
wo.user.frameworks=/Users/<YOUR_USER_NAME_HERE!>/Library/Frameworks
wo.system.frameworks=/Developer/Versions/WebObjects543/System/Library/Frameworks
wo.bootstrapjar=/Developer/Versions/WebObjects543/System/Library/WebObjects/JavaApplications/wotaskd.woa/WOBootstrap.jar
wo.network.frameworks=/Network/Library/Frameworks
wo.api.root=/Developer/ADC%20Reference%20Library/documentation/WebObjects/Reference/API
wo.network.root=/Network
wo.extensions=/Developer/Versions/WebObjects543/Library/WebObjects/Extensions
wo.user.root=/Users/<YOUR_USER_NAME_HERE!>
wo.local.frameworks=/Developer/Versions/WebObjects543/Library/Frameworks
wo.dir.local.library.frameworks=/Developer/Versions/WebObjects543/Library/Frameworks
wo.apps.root=/Developer/Versions/WebObjects543/Library/WebObjects/Applications
wo.local.root=/Developer/Versions/WebObjects543
wo.dir.user.home.library.frameworks=/Users/<YOUR_USER_NAME_HERE!>/Library/Frameworks

...

At this point, you should have a functioning WebObjects platform to work with, visit <hello world link> to test your first WebObjects application.

Video of Step 3:

Multimedia
nameWOInstallPart3.mov

Step 5:  Import Project Wonder into your Eclipse workspace

...

Note

Project Wonder is a significant part of the WebObjects experience.  Where the previous step seems to give new users the most grief now, this step will give you the most pleasure when working with WebObjects.

Video of Step 4:

Multimedia
nameWOInstallPart4.mov

 

At the end of this step, you will have Project Wonder imported into Eclipse under its own working set.  If you are unfamiliar with working sets in Eclipse, the following video will help clarify.  This video also demonstrates a "Hello World" project creation to validate proper installation.

Multimedia
nameWOInstall_WorkspaceAndHelloWorld.mov


  

Fixing Auto Launch

Q. Hi everyone. I've seen several people on the list with the same problem as this, but haven't seen it resolved yet. When launching an app on WO5.2.2 developer on Windows XP, this error message is displayed:

...

A. use the following methods in your Application class:

Code Block

/**
  * Calls _isAdditionalForeignSupportedDevelopmentPlatform
  *
  * @see com.webobjects.appserver.WOApplication#_isForeignSupportedDevelopmentPlatform()
 */
 public boolean _isForeignSupportedDevelopmentPlatform()
 {
   return (super._isForeignSupportedDevelopmentPlatform() || _isAdditionalForeignSupportedDevelopmentPlatform());
 }

 /**
  * Check for Windows XP
  * @return true if runs on XP
  */
 public boolean _isAdditionalForeignSupportedDevelopmentPlatform()
 {
   String s = System.getProperty("os.name");
   return ( s != null && s.equals("Windows XP") );
 }

...

A. When using white spaces in the project, framework path or WAR deployment etc on Windows, the white space will turn into "%20" in the path.  This will cause NSBundle.mainBundle returns null when it unable to load any bundles.  For example:  

Code Block

Example path will not work:
C:\Documents and Settings
 
will turn into this wrong path:
C:\Documents%20and%20Settings
 
Therefore, this path will work:
C:\DocumentsAndSettings

...