Changes for page Best Practices-Properties Files
Last modified by Ray Kiddy on 2009/07/29 13:11
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- 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