Here is a tutorial on installing WebObjects on Windows:
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:
Your application is not running on a supported development platform. AutoLaunch will not work.
I can cut and paste the URL into a browser manually, but I'm too lazy to do all that 'work' all day long I've tried the WOAutoOpenInBrowser setting with no luck. I've also tried setting W2K compatibilty mode for project builder and the WOOpenUrl application with no luck.
A. use the following methods in your Application class:
* 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") );
Don't Use White Spaces for Path
Q. Can someone explain why NSBundle seems have broken path on Windows, but work fine on other platforms?
Example of an exception:
java.lang.IllegalArgumentException: Attempt to insert null into an
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:
Example path will not work:
C:\Documents and Settings
will turn into this wrong path:
Therefore, this path will work:
Keep your files in path without white space seemed to be the first rule of thumb when development on Windows. Default location "C:\Documents and Setting" should not be used.