svn commit: r1667379 - /incubator/tamaya/site/trunk/content/quickstart.mdtext

[an...@apache.org]

Author: anatole
Date: Tue Mar 17 19:37:55 2015
New Revision: 1667379

URL: http://svn.apache.org/r1667379
Log:
Updated description of core functionality to current state.

Modified:
    incubator/tamaya/site/trunk/content/quickstart.mdtext

Modified: incubator/tamaya/site/trunk/content/quickstart.mdtext
URL: http://svn.apache.org/viewvc/incubator/tamaya/site/trunk/content/quickstart.mdtext?rev=1667379&r1=1667378&r2=1667379&view=diff
==============================================================================
--- incubator/tamaya/site/trunk/content/quickstart.mdtext (original)
+++ incubator/tamaya/site/trunk/content/quickstart.mdtext Tue Mar 17 19:37:55 2015
@@ -34,21 +34,38 @@ minimalistic way. FOr that add the follo
 
 Given that you can add your configuration properties to the following locations in your classpath:
 
-    META-INF/cfg/default-config.properties
-    META-INF/cfg/config.properties
+    META-INF/javaconfiguration.properties
 
-Additionally also system and environment properties are taken into account. Overall Tamaya by default defines the
-following configuration model (most significant first):
+Additionally also system properties are taken into account, hereby overriding the default properties. Overall
+Tamaya by default defines the following configuration model per default (most significant first):
 
     1. System Properties
-    2. META-INF/cfg/config.properties
-    3. META-INF/cfg/default-config.properties
-    5. Environment Properties
+    2. META-INF/cfg/javaconfiguration.properties
+
+By default you can provide multiple javaconfig.properties files, e.g. as part of multiple jars loaded into your system.
+The system internally creates one PropertySource for each file found on the classpath. All PropertySources created
+are ordered by their ordinal value (an int). These ordinal values can be either hardcoded, or be dynamically
+configurable as key within each file. The ladder can be done by defining a special Tamaya ordinal value as follows:
+
+    #override ordinal
+    tamaya.ordinal=123
+
+This assigns an ordinal of 123 to each entry in that configuration resource. Tamaya Core defines the following default
+ordinals (used, if no custom ordinal is defined):
+
+* System Properties -> 400
+* javaconfiguration.properties -> 100
+
+If you want to add additional file locations or formats or other functionality you miss, have a look at the numerous
+Tamaya extension modules (see below). Or just implement a PropertySource (or PropertySourceProvider) on your own and register
+it using the Java ServiceLoader.
 
 
 # Adding additional features
 
-Depenending on your liking you may add additional extensions such as:
+There many modules that extend the capabilities of Tamaya. These modules doe not depend on core, so alternative
+implementations of the Tamaya API should work similarly. Following a small extract of most important modules
+available (or available soon):
 
 ## Dynamic Resolution and Value Placeholders