Skip to Content
Last modified by Lazy Lazarus on 2025/03/28 23:05
From version 18.1
edited by David Avendasora
on 2008/06/23 15:47
Change comment: There is no comment for this version
To version 19.1
edited by David Avendasora
on 2008/06/23 15:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -67,13 +67,9 @@
67 67  
68 68  If the client-side application is complaining about not being able to find classes that are part of a framework when run from within Eclipse, it means the the ClasspathClient.txt is missing classpath entries. This file is not automatically maintained by WOLips (yet). Any frameworks that you import into your project must have a corrosponding entry formatted as follows:
69 69  
70 -{{noformat}}
71 -APPROOT/WebServerResources/Java/MyFramework.jar
72 -{{/noformat}}
70 +{{noformat}}APPROOT/WebServerResources/Java/MyFramework.jar{{/noformat}}
73 73  
74 74  {{note title="Be Careful"}}
75 -
76 76  Don't use the WOROOT path of the framework (WOROOT/Library/Frameworks/MyFramework.framework/WebServerResources/Java/MyFramework.jar)
77 77   because this is only valid for the core WebObjects frameworks. Any other frameworks (yours, Wonder, etc) need to be located in the APPROOT.
78 -
79 79  {{/note}}