Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 13.1
edited by Denis Frolov
on 2007/07/17 10:04
Change comment: There is no comment for this version
To version 11.1
edited by David Holt
on 2008/09/11 19:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfrolov
1 +XWiki.dholt
Content
... ... @@ -2,10 +2,22 @@
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 -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 +{{info title="Alternate method for getting started with BugTracker"}}
6 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 +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 +
7 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.
8 8  
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 +
9 9  [[image:Context-023.jpg]]
10 10  [[image:Context-024.jpg]]
11 11  [[image:Context-025.jpg]]
... ... @@ -36,20 +36,31 @@
36 36  
37 37  ----
38 38  
51 +{{id value="Configuration"}}{{/id}}
52 +
39 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 40  
55 +{{info title="Update: Sept 11, 2008 How to enable properties for databases other than Derby (FrontBase,PostgreSQL)"}}
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
60 +
61 +
62 +{{/info}}
63 +
41 41  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]]
42 42  
43 43  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:
44 44  
45 -#ERXConfigurationManager properties moved in from Properties.ak
46 -#Original Settings for Postgresql
47 -#Changed to Frontbase
68 +ERXConfigurationManager properties moved in from Properties.ak
69 +Original Settings for Postgresql
70 +Changed to Frontbase
48 48  dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug
49 49  dbConnectUserGLOBAL=//system
50 50  dbConnectPluginGLOBAL=Frontbase
51 -#dbConnectDriverGLOBAL=org.postgresql.Driver
52 -#dbConnectPasswordGLOBAL =
74 +dbConnectDriverGLOBAL=org.postgresql.Driver
75 +dbConnectPasswordGLOBAL =
53 53  dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
54 54  er.javamail.adminEmail=foo@localhost.com//
55 55  
... ... @@ -57,6 +57,23 @@
57 57  
58 58  [[image:Context-036.jpg]]
59 59  
83 +{{info title="MySQL Configuration for BugTracker"}}
84 +
85 +* Create a database named "bug" in your MySQL development database
86 +* Create a user and password with all privileges for that database (or use your mysql root user and password if you wish)
87 +* Add the following properties to the Properties file in BugTracker using the user and password from the previous step
88 +
89 +dbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true
90 +dbConnectUserGLOBAL=user
91 +dbConnectPasswordGLOBAL=password
92 +dbConnectPluginGLOBAL=
93 +dbConnectDriverGLOBAL=
94 +dbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes
95 +er.javamail.adminEmail=foobar@domain.com
96 +
97 +
98 +{{/info}}
99 +
60 60  ----
61 61  
62 62  Make sure that the build path contains the plugin for your database;
... ... @@ -99,4 +99,4 @@
99 99  
100 100  ----
101 101  
102 -12. Explore!!
142 +12. Explore