Skip to Content
Last modified by Markus Ruggiero on 2025/10/24 16:07
From version 20.1
edited by David Avendasora
on 2009/06/25 10:48
Change comment: There is no comment for this version
To version 27.1
edited by Ray Kiddy
on 2009/07/29 13:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Best Practices
1 +Best Practices-Properties Files
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.avendasora
1 +XWiki.kiddyr
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 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 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.
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 8  
9 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 10  
... ... @@ -14,15 +14,15 @@
14 14  
15 15  === Database Connection Properties ===
16 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.
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 so that you set connection info for each user, for development or for deployment.
18 18  
19 19  ==== Model-Specific Connection Properties ====
20 20  
21 21  {{noformat}}
22 22  
23 -MyEOModel.URL =
24 -MyEOModel.DBUser =
25 -MyEOModel.DBPassword =
23 +MyEOModel.URL =
24 +MyEOModel.DBUser =
25 +MyEOModel.DBPassword =
26 26  MyEOModel.DBDriver =
27 27  MyEOModel.DBPlugin =
28 28  MyEOModel.DBJDBCInfo =