Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 30.1
edited by David Holt
on 2007/10/31 20:40
Change comment: There is no comment for this version
To version 38.1
edited by Pascal Robert
on 2012/07/27 20:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dholt
1 +XWiki.probert
Content
... ... @@ -1,127 +1,16 @@
1 1  **Getting Started with BugTracker**
2 2  
3 -~1. Import the source code folders needed for BugTracker either [[from local Wonder source tree>>http://wiki.objectstyle.org/confluence/display/WONDER/Working+with+Wonder+source+in+Eclipse]] or from Wonder CVS server as discussed below.
3 +BugTracker is an example application that exposes a lot of Wonder functionalities. It is especially true if you want to have a look at DirectToWeb (D2W) since BugTracker have a lot of custom D2W rules.
4 4  
5 -The next three screenshots are showing the folders that can be found on the CVS server for Wonder. I have split them up because all the folders don't fit on the screen at once As you can see, the folders that are necessary are found in several different sub-folders.
5 +You can listen to a good introduction to BugTracker by listening to the [[presentation>>http://www.wocommunity.org/podcasts/wowodc/west08/WOWODC07_D2W.mp4]] made at WOWODC 2007.
6 6  
7 -You may need to adjust the exact folders you import depending on the database you plan to use. In this case, I have added the FrontBase plugin as well as all the other frameworks that BugTracker expects to find in its build path.
7 +To look at BugTracker, you will need to g[[et the Wonder Source Code>>Getting the Wonder Source Code]] of Project Wonder. Once it's done and that you have imported the BugTracker project into Eclipse, you will see the following files: [[image:BugTrackerProject.png||border="1"]]
8 +To launch BugTracker, right-click **BugTracker.launch** and select **Run As** > **BugTracker**. It will launch BugTracker with a in-memory database, which is perfect to explore the application.
8 8  
9 -[[image:Context-023.jpg]]
10 -[[image:Context-024.jpg]]
11 -[[image:Context-025.jpg]]
10 +You should see a login screen. Your default administrative user is "admin" with password "admin"
12 12  
13 -----
14 -
15 -2. Check out the folders into their own projects in your workspace.
16 -
17 -[[image:Context-026.jpg]]
18 -
19 -----
20 -
21 -3. Your workspace should look roughly like this once it has completed rebuilding:
22 -
23 -[[image:Context-027.jpg]]
24 -
25 -----
26 -
27 -4. First order of business is to find your Properties file by turning off the filter that is on by default:
28 -
29 -[[image:Context-028.jpg]]
30 -
31 -----
32 -
33 -5. Uncheck the item selected in the image below:
34 -
35 -[[image:Context-029.jpg]]
36 -
37 -----
38 -
39 -6. Change the Properties located in the resources folder to match the requirements for your database. Wonder applications need Properties files to manage their configuration correctly. There are a number of different places in the Wonder frameworks that application properties will be read from. In the original example, the Database connection properties are taken from a logged in user's properties file, in this case it is named "Properties.ak". I moved the relevant lines to the Application Properties file that described the Global connection dictionary for BugTracker to access my FrontBase database. Alternatively (a recommended way) you can create your own "Properties.username" file by duplicating "Properties.ak"
40 -
41 -{{warning title="Missing Properties"}}
42 -
43 -The current Wonder source (Oct 31,2007) requires the addition of this property to he Properties file in BugTracker to run properly (Can someone commit this please?)
44 -
45 -er.extensions.ERXRaiseOnMissingEditingContextDelegate=false
46 -
47 -{{/warning}}
48 -
49 -You can either set Global properties for your database, or you can set them for a specific model. See the Wonder docs for more information about Properties files and database configuration [[ERXConfigurationManager documentation>>http://webobjects.mdimension.com/wonder/api/er/extensions/ERXConfigurationManager.html]]
50 -
51 -Here are the Global database connection settings I used for FrontBase. If you are using a different setup, you may want to ask on the mailing list for guidance:
52 -
53 -ERXConfigurationManager properties moved in from Properties.ak
54 -Original Settings for Postgresql
55 -Changed to Frontbase
56 -dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug
57 -dbConnectUserGLOBAL=//system
58 -dbConnectPluginGLOBAL=Frontbase
59 -dbConnectDriverGLOBAL=org.postgresql.Driver
60 -dbConnectPasswordGLOBAL =
61 -dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
62 -er.javamail.adminEmail=foo@localhost.com//
63 -
64 -You can see the Properties file that you are editing in the following screenshot:
65 -
66 -[[image:Context-036.jpg]]
67 -
68 -{{info title="MySQL Configuration for BugTracker"}}
69 -
70 -* Create a database named "bug" in your MySQL development database
71 -* Create a user and password with all privileges for that database (or use your mysql root user and password if you wish)
72 -* Add the following properties to the Properties file in BugTracker using the user and password from the previous step
73 -
74 -dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true
75 -dbConnectUserGLOBAL=user
76 -dbConnectPasswordGLOBAL=password
77 -dbConnectPluginGLOBAL=
78 -dbConnectDriverGLOBAL=
79 -dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes
80 -er.javamail.adminEmail=foobar@domain.com
81 -
82 -
83 -{{/info}}
84 -
85 -----
86 -
87 -Make sure that the build path contains the plugin for your database;
88 -
89 -[[image:Context-030.jpg]]
90 -
91 -----
92 -
93 -7. Now we want to run the app. The Wonder team has set it up so that you can generate all necessary tables and populate them when you launch the BugTracker application for the first time using a special launch configuration.
94 -
95 -You'll see BugTracker launch configurations for creating, creating without dropping, and normal launching. We need to select the BugTracker (create without drop) launch configuration for the initial setup.
96 -
97 -[[image:Context-031.jpg]]
98 -
99 -----
100 -
101 -8. We do that by selecting Run as > Run...
102 -
103 -[[image:Context-032.jpg]]
104 -
105 -----
106 -
107 -9. In the resulting dialog box, select BugTracker (create without drop). If you try to use (create) you'll get a bunch of errors complaining about lack of tables in the database.
108 -
109 -[[image:Context-033.jpg]]
110 -
111 -----
112 -
113 -10. You'll see a long list of things being done in your console window that takes several minutes. When you get the final Done message, your database is set up and ready to go. You can log into your database to confirm that the tables have been magically created and populated.
114 -
115 -Now select BugTracker as your launch configuration to start the application:
116 -
117 -[[image:Context-034.jpg]]
118 -
119 -----
120 -
121 -~11. You should see a login screen. Your default administrative user is "admin" with password "admin"
122 -
123 123  [[image:Context-035.jpg]]
124 124  
125 125  ----
126 126  
127 -12. Explore
16 +Explore