Skip to Content

Changes for page Development on Windows

Last modified by Pascal Robert on 2012/07/21 14:37
From version 10.1
edited by Pascal Robert
on 2012/07/20 11:35
Change comment: There is no comment for this version
To version 6.1
edited by Pascal Robert
on 2007/09/03 14:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Development on Windows
1 +Web Applications-Development-Development on Windows
Content
... ... @@ -1,3 +1,7 @@
1 +Here is a tutorial on installing WebObjects on Windows:
2 +
3 +[[http://www.tetlabors.de/wo/setup_webobjects_on_windows.html]]
4 +
1 1  == Fixing Auto Launch ==
2 2  
3 3  //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~://
... ... @@ -14,7 +14,7 @@
14 14  
15 15  {{code}}
16 16  
17 -/**
21 + /**
18 18   * Calls _isAdditionalForeignSupportedDevelopmentPlatform
19 19   *
20 20   * @see com.webobjects.appserver.WOApplication#_isForeignSupportedDevelopmentPlatform()
... ... @@ -34,40 +34,8 @@
34 34   return ( s != null && s.equals("Windows XP") );
35 35   }
36 36  
37 -{{/code}}
38 38  
39 - StefanKlein
40 40  
41 -== Don't Use White Spaces for Path ==
42 -
43 -//Q. Can someone explain why NSBundle seems have broken path on Windows, but work fine on other platforms? //
44 -
45 -//   Example of an exception~://
46 -
47 -{{panel}}
48 -
49 -java.lang.IllegalArgumentException: Attempt to insert null into an
50 -com.webobjects.foundation.NSMutableArray.
51 -at com.webobjects.foundation.NSMutableArray.addObject(NSMutableArray.java:239)
52 -at com.webobjects.eoaccess.EOModelGroup.modelGroupForLoadedBundles(EOModelGroup.java:700)
53 -at com.webobjects.eoaccess.EOModelGroup.globalModelGroup(EOModelGroup.java:306)
54 -at com.webobjects.eoaccess.EOModelGroup.defaultGroup(EOModelGroup.java:333)
55 -
56 -{{/panel}}
57 -
58 -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:  
59 -
60 -{{code}}
61 -
62 -Example path will not work:
63 -C:\Documents and Settings
64 - 
65 -will turn into this wrong path:
66 -C:\Documents%20and%20Settings
67 - 
68 -Therefore, this path will work:
69 -C:\DocumentsAndSettings
70 -
71 71  {{/code}}
72 72  
73 -Keep your files in path without white space seemed to be the first rule of thumb when development on Windows.  Default location "C:ocuments and Setting" should not be used.
45 + StefanKlein