Changes for page About the Properties file
Last modified by Theodore Petrosky on 2016/06/28 12:30
From version 17.1
edited by Kieran Kelleher
on 2007/10/10 15:48
on 2007/10/10 15:48
Change comment:
There is no comment for this version
To version 18.1
edited by Pascal Robert
on 2007/12/15 18:30
on 2007/12/15 18:30
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. kieran1 +XWiki.probert - Content
-
... ... @@ -1,17 +1,15 @@ 1 1 == Introduction == 2 2 3 -Most applications need a place to hold application configuration information. In java, a file with simple entries in traditional [[java.util.Properties>>http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html#load(java.io.InputStream)]] format can be read and merged with the System properties, usually at application launch time. The traditional (as distinct from the XML format supported by java 1.5) simple format of a java properties file is like this: 3 +Most applications need a place to hold application configuration information. In java, a file with simple entries in traditional [[java.util.Properties>>url:http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html#load(java.io.InputStream)||shape="rect"]] format can be read and merged with the System properties, usually at application launch time. The traditional (as distinct from the XML format supported by java 1.5) simple format of a java properties file is like this: 4 4 5 5 {{panel}} 6 - 7 7 myproperty=12345 8 -myotherproperty=This is a sentence 9 - 7 + myotherproperty=This is a sentence 10 10 {{/panel}} 11 11 12 -WebObjects manages application preferences using a similar mechanism implemented by its [[com.webobjects.foundation.NSProperties>>http://developer.apple.com/documentation/ WebObjects/Reference/API/com/webobjects/foundation/NSProperties.html]] class. The file format is as per the spec. In many references you will see specs say that a certain file is in java.io.Properties file format, however if I am not mistaken, they really mean the java.util.Properties, since even as far back as Java 1.1 API, there was no such class as java.io.Properties.10 +WebObjects manages application preferences using a similar mechanism implemented by its [[com.webobjects.foundation.NSProperties>>url:http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/com/webobjects/foundation/NSProperties.html||shape="rect"]] class. The file format is as per the spec. In many references you will see specs say that a certain file is in java.io.Properties file format, however if I am not mistaken, they really mean the java.util.Properties, since even as far back as Java 1.1 API, there was no such class as java.io.Properties. 13 13 14 -In any case, WebObjects directly supports the use of [[Java 1.4 style properties>>http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html]] entries in the file named Resources/Properties in the woa and framework bundle format. 12 +In any case, WebObjects directly supports the use of [[Java 1.4 style properties>>url:http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html||shape="rect"]] entries in the file named Resources/Properties in the woa and framework bundle format. 15 15 16 16 == Using Properties in WebObjects == 17 17 ... ... @@ -71,4 +71,4 @@ 71 71 72 72 == Conclusion == 73 73 74 -So, bysimply putting aplication and logging properties into the Properties file means that all your configuration is in one place **and** each member of the development team can override those deployment settings with their own user based Properties files. Useful when they want to add DEBUG logging on stuff that other team members are not interested in.72 +So, simply putting application and logging properties into the Properties file means that all your configuration is in one place **and** each member of the development team can override those deployment settings with their own user based Properties files. Useful when they want to add DEBUG logging on stuff that other team members are not interested in.