Wiki source code of Best Practices

Version 22.1 by David Avendasora on 2009/06/25 10:47

Show last authors
1 === Properties Files ===
2
3 ==== User-Specific Properties Files ====
4
5 You can have any number of **Properties.username** files in your project's Resources directory in-addition-to the default **Properties** file. These Properties.username files will automatically load based on which user is launching the application. This allows you to have custom logging, email, database, etc configuration settings for each developer.
6
7 This capability can also be (ab)used in combinination with the Launch parameter **-Duser.name** to specify Production vs Staging/Development properties. For example: a launch parameter of **-Duser.name=deployment** will cause **Properties.deployment** to be read when the application in launched.
8
9 This can be very useful for automatically changing database connection configurations based on whether or not an application is being run in Production or Development.
10
11 ==== Development Only Properties File ====
12
13 You can set properties that will only be active if the project is run in Development mode by creating a **Properties.dev** file. It will be loaded for all users.
14
15 === Database Connection Properties ===
16
17 While the easiest place to set connection properties is in the EOModel, a better place to put them is in the Properties system, that way you can leverage the flexibility of launch-time loading of Properties.
18
19 ==== Model-Specific Connection Properties ====
20
21 MyEOModel.URL =
22 MyEOModel.DBUser =
23 MyEOModel.DBPassword =
24 MyEOModel.DBDriver =
25 MyEOModel.DBPlugin =
26 MyEOModel.DBJDBCInfo =
27
28 ==== Global Connection Properties ====
29
30 These settings will allow you to set the connection properties for all the EOModels in your project.
31
32 {{noformat}}
33
34 dbConnectURLGLOBAL =
35 dbConnectUserGLOBAL =
36 dbConnectPasswordGLOBAL =
37 dbConnectDriverGLOBAL =
38 dbEOPrototypesEntityGLOBAL =
39
40 {{/noformat}}