Skip to Content
Last modified by Pascal Robert on 2007/12/15 18:15
From version 33.1
edited by Kieran Kelleher
on 2007/01/16 13:58
Change comment: There is no comment for this version
To version 32.1
edited by Kieran Kelleher
on 2007/01/16 13:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,13 +7,6 @@
7 7  
8 8  === How To ===
9 9  
10 -===== Before you start, edit your Package Explorer filters so that we can really "see" the files in our project, especially so we can check if our project was created correctly by the wizard later on. To do this simply select Filters from the Package Explorer contextual menu as shown below: =====
11 -
12 -[[image:packageExplorer-filters.jpg]]
13 -
14 -... and then deselect everything except the ones show here. This of course is a user preference, but at least your screen will match my initial project picture shown here if you do as I tell you!
15 -[[image:javaElementFilters.jpg]]
16 -
17 17  ===== First create the project in your Eclipse workspace. =====
18 18  
19 19  Right-click in Package Explorer view of the WOLips perspective and select New->Other.
... ... @@ -25,32 +25,4 @@
25 25  Next enter a project name and click Finish
26 26  [[image:WOnderFramework-projectname.jpg]]
27 27  
28 -WOLips Bug: If your new framework project DOES NOT look like the one in the picture then you have come across a known elusive WOLips bug that the team is trying to solve. In the case that your project does not look like this, the fix is to select the project and then select the Project->Close in the main menu bar. Afterward select Project->Open and then expand your project and it should be OK.
29 -
30 -Another Minor Bug: In the latest build I was using, the default framework project does not contain a folder named 'Components' which it needs to have a successful build later. So just create a new folder in the project named Components
31 -
32 -===== Next add any 3rd party jar files to your project that you want bundled with this framework. This is probably the "best practice" way to make 3rd party jars available to your WebObjects apps rather than stuffing them into /Library/WebObjects/Extensions. =====
33 -
34 -To do this simply locate the jar in the Finder and drag and drop it on the Libraries folder in your project as shown here:
35 -[[image:dragJarToLibraries.jpg]]
36 -
37 -===== Next, edit the build path so that it sees the classes in this jar. Right-click on the project -> Build Path -> Configure Build Path. =====
38 -
39 -Click on the Libraries tab.
40 -Click the Add Jars button and navigate to the jar inside your project.
41 -Select the jar and click OK.
42 -[[image:buildPath-jarSelection.jpg]]
43 -
44 -Adding dependencies on other frameworks can be done at this stage if your wish. The procedure is the same as for adding framework dependencies to a WOApplication which also has a tutorial.
45 -
46 -===== Now I want to create a package for my reusable classes. =====
47 -
48 -Right-click on the Sources folder and select New -> Package as shown here:
49 -[[image:Sources-new-package.jpg]]
50 -
51 -Enter a name for the package and Eclipse automatically creates the appropriate folder structure in the file system:
52 -[[image:NewJavaPackage.jpg]]
53 -
54 -===== Add classes to your package. You can drag java files from the file system or XCode to the package: =====
55 -
56 -[[image:dragClassToPackage.jpg]]
21 +(( Under Construction )) (I just noticed that the WOnderFramework wizard is hosed in latest version of WOLips (3769) ... I will come back to this later