Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 11.1
edited by David Holt
on 2008/09/11 19:47
Change comment: There is no comment for this version
To version 15.1
edited by Kieran Kelleher
on 2007/10/31 16:14
Change comment: Added MySQL config info and note on missing ec delegate property

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dholt
1 +XWiki.kieran
Content
... ... @@ -2,22 +2,10 @@
2 2  
3 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.
4 4  
5 -{{info title="Alternate method for getting started with BugTracker"}}
6 -
7 -If you're just exploring BugTracker, you may prefer to use the method outlined on [this page|Getting Started with BugTracker Alternate method] that depends on installed Wonder frameworks instead of importing the Wonder source into your workspace.
8 -
9 -{{/info}}
10 -
11 11  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.
12 12  
13 13  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.
14 14  
15 -{{warning title="Missing Projects from the screenshots below"}}
16 -
17 -BugTracker has new dependencies on DerbyPlugin and ERChronic since these screenshots were taken. Make sure to import them into your workspace as well.
18 -
19 -{{/warning}}
20 -
21 21  [[image:Context-023.jpg]]
22 22  [[image:Context-024.jpg]]
23 23  [[image:Context-025.jpg]]
... ... @@ -48,18 +48,15 @@
48 48  
49 49  ----
50 50  
51 -{{id value="Configuration"}}{{/id}}
52 -
53 53  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"
54 54  
55 -{{info title="Update: Sept 11, 2008 How to enable properties for databases other than Derby (FrontBase,PostgreSQL)"}}
41 +{{warning title="Missing Properties"}}
56 56  
57 -* 3 Default Global database properties files are now included with BugTracker. Please see Properties.Derby,Properties.FrontBase,Properties.PostgreSQL
58 -* In the 3 launch configurations (discussed below in point 7) user.name=Derby is now set by default.
59 -* You can swap out Derby for your favourite database (i.e. user.name=FrontBase or user.name=PostgreSQL) in all 3 launch configurations if you want to use your database properties instead of the default Derby
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?)
60 60  
45 +er.extensions.ERXRaiseOnMissingEditingContextDelegate=false
61 61  
62 -{{/info}}
47 +{{/warning}}
63 63  
64 64  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]]
65 65  
... ... @@ -86,7 +86,7 @@
86 86  * Create a user and password with all privileges for that database (or use your mysql root user and password if you wish)
87 87  * Add the following properties to the Properties file in BugTracker using the user and password from the previous step
88 88  
89 -dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true
74 +dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capializeTypenames=true
90 90  dbConnectUserGLOBAL=user
91 91  dbConnectPasswordGLOBAL=password
92 92  dbConnectPluginGLOBAL=