Skip to Content
Last modified by Pascal Robert on 2012/07/27 20:28
From version 24.1
edited by David Avendasora
on 2011/04/25 12:42
Change comment: There is no comment for this version
To version 28.1
edited by David Holt
on 2007/06/20 20:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.dholt
Content
... ... @@ -1,72 +1,69 @@
1 1  **Getting Started with BugTracker**
2 2  
3 -There are different ways to build the BugTracker application. If you are going to be making changes to the project and its dependent frameworks and experimenting with them, you will probably want to open the projects in eclipse with WOLips. If you just want to see the app work, you can check out the code, build it with ant and run it from the /Roots directory. See [[Downloading, Building, Installing and Upgrading Wonder Source Code]] page for information on getting the projects' source and building it.
3 +~1. Import the following source code folders from CVS according to the [[tutorial>>http://wiki.objectstyle.org/confluence/display/WOL/Project+Wonder+woa+with+Linked+Source]]. 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.
4 4  
5 -If you build the app with ant, launching it may be as simple (once some things are set up) as:
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.
6 6  
7 -{{code}}
7 +[[image:Context-023.jpg]]
8 +[[image:Context-024.jpg]]
9 +[[image:Context-025.jpg]]
8 8  
9 -( cd ~/Roots/BugTracker.woa ;
10 -  ./BugTracker \
11 -    -Der.javamail.centralize=false \
12 -    -Der.extensions.ERXApplication.developmentMode=true \
13 -    -DdbConnectURLGLOBAL=jdbc:mysql://localhost/bug?capitalizeTypenames=true \
14 -    -DdbConnectUserGLOBAL=ray \
15 -    -DdbConnectPasswordGLOBAL=secretSauce \
16 -    -DdbConnectPluginGLOBAL= \
17 -    -DdbConnectDriverGLOBAL= \
18 -    -DdbEOPrototypesEntityGLOBAL=EOJDBCMySQLPrototypes )
11 +----
19 19  
20 -{{/code}}
13 +2. Check out the folders into their own projects in your workspace.
21 21  
22 -If you want to build the application in eclipse, you may need to set the framework dependencies of the project. There are two ways of doing this. You can either open all the dependent frameworks in eclipse and then eclipse will track and build everything, or you can point the open project(s) to installed versions of the framework, as installed. Instructions for these two methods of managing framework dependencies is at [[Add a Framework Dependency>>WOL:Add a Framework Dependency]]. The frameworks that the BugTracker application may depend on are:
15 +[[image:Context-026.jpg]]
23 23  
24 -* Ajax.framework
25 -* BTBusinessLogic.framework
26 -* DerbyPlugin.framework
27 -* ERCalendar.framework
28 -* ERCaptcha.framework
29 -* ERCoreBusinessLogic.framework
30 -* ERDirectToWeb.framework
31 -* ERExcelLook.framework
32 -* ERExtensions.framework
33 -* ERJars.framework
34 -* ERJavaMail.framework
35 -* ERPlot.framework
36 -* ERPrototypes.framework
37 -* ERRest.framework
38 -* ERSelenium.framework
39 -* JavaWOExtensions.framework
40 -* WOOgnl.framework
41 -* ExcelGenerator.framework
42 -* FrontBasePlugin.framework
43 -* PostgresPlugin.framework
44 -
45 45  ----
46 46  
47 -if you open all the dependent projects in eclipse, your workspace should look roughly like this once it has completed rebuilding:
19 +3. Your workspace should look roughly like this once it has completed rebuilding:
48 48  
49 49  [[image:Context-027.jpg]]
50 50  
51 51  ----
52 52  
53 -{{id value="Configuration"}}{{/id}}
25 +4. First order of business is to find your Properties file by turning off the filter that is on by default:
54 54  
55 -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". Or you may uncomment the property set that you want to use in the Resources/Properties file. See Project Wonder Properties FilesWO:Project Wonder Properties Files for more information on configuring the application.
27 +[[image:Context-028.jpg]]
56 56  
57 -You can see a Properties file in the following screenshot:
29 +----
58 58  
31 +5. Uncheck the item selected in the image below:
32 +
33 +[[image:Context-029.jpg]]
34 +
35 +----
36 +
37 +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.
38 +
39 +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]]
40 +
41 +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:
42 +
43 +#ERXConfigurationManager properties moved in from Properties.ak
44 +#Original Settings for Postgresql
45 +#Changed to Frontbase
46 +dbConnectURLGLOBAL=jdbc:frontbase:~/~/localhost/bug
47 +dbConnectUserGLOBAL=//system
48 +dbConnectPluginGLOBAL=Frontbase
49 +#dbConnectDriverGLOBAL=org.postgresql.Driver
50 +#dbConnectPasswordGLOBAL =
51 +dbEOPrototypesEntityGLOBAL=EOJDBCFrontBasePrototypes
52 +er.javamail.adminEmail=foo@localhost.com//
53 +
54 +You can see the Properties file that you are editing in the following screenshot:
55 +
59 59  [[image:Context-036.jpg]]
60 60  
61 61  ----
62 62  
63 -Make sure that the build path contains the plugin for your database that you are using:
60 +Make sure that the build path contains the plugin for your database;
64 64  
65 65  [[image:Context-030.jpg]]
66 66  
67 67  ----
68 68  
69 -There is support for launching the app in different ways so that, the database tables can be created or deleted and then re-created.
66 +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.
70 70  
71 71  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.
72 72  
... ... @@ -74,19 +74,19 @@
74 74  
75 75  ----
76 76  
77 -Select the 'Run As...' menu option from the 'Run' menu in eclipse:
74 +8. We do that by selecting Run as > Run...
78 78  
79 79  [[image:Context-032.jpg]]
80 80  
81 81  ----
82 82  
83 -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.
80 +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.
84 84  
85 85  [[image:Context-033.jpg]]
86 86  
87 87  ----
88 88  
89 -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.
86 +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.
90 90  
91 91  Now select BugTracker as your launch configuration to start the application:
92 92  
... ... @@ -94,10 +94,10 @@
94 94  
95 95  ----
96 96  
97 -You should see a login screen. Your default administrative user is "admin" with password "admin"
94 +~11. You should see a login screen. Your default administrative user is "admin" with password "admin"
98 98  
99 99  [[image:Context-035.jpg]]
100 100  
101 101  ----
102 102  
103 -Explore
100 +12. Explore!!