Changes for page Development on Windows

Last modified by Pascal Robert on 2012/07/21 14:37

From version 8.1
edited by mychng
on 2009/04/30 01:39
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mychng
1 +XWiki.probert
Content
... ... @@ -18,7 +18,7 @@
18 18  
19 19  {{code}}
20 20  
21 -/**
21 + /**
22 22   * Calls _isAdditionalForeignSupportedDevelopmentPlatform
23 23   *
24 24   * @see com.webobjects.appserver.WOApplication#_isForeignSupportedDevelopmentPlatform()
... ... @@ -38,43 +38,8 @@
38 38   return ( s != null && s.equals("Windows XP") );
39 39   }
40 40  
41 -{{/code}}
42 42  
43 - StefanKlein
44 44  
45 -== Don't Use White Spaces for Path ==
46 -
47 -//Q. Can someone explain why NSBundle seems have broken path on Windows, but work fine in other platforms? //
48 -
49 -//   Example of an exception~://
50 -
51 -{{panel}}
52 -
53 -java.lang.IllegalArgumentException: Attempt to insert null into an
54 -com.webobjects.foundation.NSMutableArray.
55 -at com.webobjects.foundation.NSMutableArray.addObject(NSMutableArray.java:239)
56 -at com.webobjects.eoaccess.EOModelGroup.modelGroupForLoadedBundles(EOModelGroup.java:700)
57 -at com.webobjects.eoaccess.EOModelGroup.globalModelGroup(EOModelGroup.java:306)
58 -at com.webobjects.eoaccess.EOModelGroup.defaultGroup(EOModelGroup.java:333)
59 -
60 -{{/panel}}
61 -
62 -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:  
63 -
64 -{{code}}
65 -
66 -Example path will not work:
67 -C:\Documents and Settings
68
69 -will turn into this wrong path:
70 -C:\Documents%20and%20Settings
71
72 -Therefore, this path will work:
73 -C:\DocumentsAndSettings
74 -
75 75  {{/code}}
76 76  
77 -
78 -\\\\
79 -
80 -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