Last modified by Pascal Robert on 2007/12/15 18:15

From version 38.1
edited by Kieran Kelleher
on 2007/01/16 14:25
Change comment: There is no comment for this version
To version 39.1
edited by Kieran Kelleher
on 2007/01/16 14:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  === Introduction ===
2 2  
3 -So, you have built the mother of all WebObjects apps in XCode or Eclipse with everything in the default package (or not ;)). The time has come where you want a make a new WebObjects application that re-uses some of the functionality you have already created in bigApp.woa.
3 +So, you have built the mother of all WebObjects apps in XCode or Eclipse with everything in the default package (or not). The time has come where you want a make a new WebObjects application that re-uses some of the functionality you have already created in bigApp.woa.
4 4  This article explains how to create a framework in Eclipse that can be used with your WebObjects projects. The resulting framework can be used in WOLips or XCode projects. In this example a framework is created that consists of class(es) that were in the default package of a WebObjects application and the 3rd party jar dependencies were originally in /Library/WebObjects/Extensions. The resulting framework bundle will encompass the 3rd party jar and the custom java classes that are moved from the original WO project.
5 5  Disclaimer: I am still relatively new to Eclipse, so if you see a smarter way to do this, then feel free to edit this wiki page.
6 6  Also, at the time of writing this article I was using Eclipse 3.2.1 with WOLips build #3769.
... ... @@ -59,12 +59,12 @@
59 59  
60 60  [[image:dragClassToPackage.jpg]]
61 61  
62 -===== Cleanup Time =====
62 +===== Cleanup Time! =====
63 63  
64 -Eclipse will check and compile your classes and sprinkle red x's and yellow exclamations on the areas needing your attention. (Isn't Eclipse just great ... intelligent assistance, refactoring, etc.) Anyway go ahead and fix/refactor to fix code problems and resolve dependencies. There is nothing like trying to package a large "default package" app to show you where you have opportunities to clean up dependencies or to show you dependencies you did not realize you had
65 -[[image:codeCleanUp.jpg]]
64 +Eclipse will check and compile your classes and sprinkle red x's and yellow exclamations on the areas needing your attention. (Isn't Eclipse just great ... intelligent assistance, refactoring, etc.) Anyway go ahead and fix/refactor to fix code problems and resolve dependencies. There is nothing like trying to package a large "default package" app to show you where you have opportunities to clean up dependencies or to show you dependencies you did not realize you had!
65 +codeCleanUp.jpg
66 66  
67 67  ===== Install The Framework =====
68 68  
69 69  Building and/or installing is the same as for WOApplications in Eclipse
70 -[[image:installFramework.jpg]]
70 +installFramework.jpg