Changes for page Getting Started with BugTracker

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.dholt
	1	+XWiki.kieran

Content

...	...	@@ -1,96 +1,72 @@
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	+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 [[Download Wonder Source, Build, Install and Upgrade]] page for information on getting the projects' source and building it.
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	+If you build the app with ant, launching it may be as simple (once some things are set up) as:
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	+{{code}}
8	8
9		-[[image:Context-023.jpg]]
10		-[[image:Context-024.jpg]]
11		-[[image:Context-025.jpg]]
	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 )
12	12
13		-----
	20	+{{/code}}
14	14
15		-2. Check out the folders into their own projects in your workspace.
	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:
16	16
17		-[[image:Context-026.jpg]]
	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
18	18
19	19	----
20	20
21		-3. Your workspace should look roughly like this once it has completed rebuilding:
	47	+if you open all the dependent projects in eclipse, your workspace should look roughly like this once it has completed rebuilding:
22	22
23	23	[[image:Context-027.jpg]]
24	24
25	25	----
26	26
27		-4. First order of business is to find your Properties file by turning off the filter that is on by default:
	53	+{{id value="Configuration"}}{{/id}}
28	28
29		-[[image:Context-028.jpg]]
	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.
30	30
31		-----
	57	+You can see a Properties file in the following screenshot:
32	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	66	[[image:Context-036.jpg]]
67	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	85	----
86	86
87		-Make sure that the build path contains the plugin for your database;
	63	+Make sure that the build path contains the plugin for your database that you are using:
88	88
89	89	[[image:Context-030.jpg]]
90	90
91	91	----
92	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.
	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.
94	94
95	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	96
...	...	@@ -98,19 +98,19 @@
98	98
99	99	----
100	100
101		-8. We do that by selecting Run as > Run...
	77	+Select the 'Run As...' menu option from the 'Run' menu in eclipse:
102	102
103	103	[[image:Context-032.jpg]]
104	104
105	105	----
106	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.
	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.
108	108
109	109	[[image:Context-033.jpg]]
110	110
111	111	----
112	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.
	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.
114	114
115	115	Now select BugTracker as your launch configuration to start the application:
116	116
...	...	@@ -118,10 +118,10 @@
118	118
119	119	----
120	120
121		-~11. You should see a login screen. Your default administrative user is "admin" with password "admin"
	97	+You should see a login screen. Your default administrative user is "admin" with password "admin"
122	122
123	123	[[image:Context-035.jpg]]
124	124
125	125	----
126	126
127		-12. Explore
	103	+Explore