tamaya-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anat...@apache.org
Subject svn commit: r1645079 - /incubator/tamaya/site/trunk/content/modules.mdtext
Date Fri, 12 Dec 2014 21:26:44 GMT
Author: anatole
Date: Fri Dec 12 21:26:44 2014
New Revision: 1645079

URL: http://svn.apache.org/r1645079
Log:
CMS commit to tamaya by anatole

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

Modified: incubator/tamaya/site/trunk/content/modules.mdtext
URL: http://svn.apache.org/viewvc/incubator/tamaya/site/trunk/content/modules.mdtext?rev=1645079&r1=1645078&r2=1645079&view=diff
==============================================================================
--- incubator/tamaya/site/trunk/content/modules.mdtext (original)
+++ incubator/tamaya/site/trunk/content/modules.mdtext Fri Dec 12 21:26:44 2014
@@ -121,6 +121,42 @@ as valid input formats. It is capable of
 Additionally the core part provides a _Environment_ implementation that maps CLI arguments,
 system and environment properties into a _root_ Environment.
 
+The core part by default is not considered to define how you should organize your configuration.
+Different needs and usage scenarios still require _Tamaya_ to be very flexible, consider
the
+following aspects that theoretically may be completely different for different usage scenarios/
+companies:
+
+* Configuration Formats
+* Configuration Locations
+* Configuration Technology (files, remote resources, classpath, database, ReST, ...)
+* Configuration Levels
+* Configuration Overriding Policies (aka duplicate handling and conflict resolution)
+* Configuration Isoolation (ear, war, rar, shared classloaders, paas, saas, multi tenancy,
+  etc).
+* Configuration Access Policies (security constraints, encryption, ...)
+* Configuration Granularity (overall, solution, products, plugins, package, class, ...)
+* Configuration Context (in relation to the current _Environment_)
+* ... (and more)
+
+All these aspects are defined in a so called configuration **meta-model**. So basically 
+you will additionally have to
+
+* choose a prebuilt meta-model provided with the metamodels module part of _Tamaya_
+* implement your own meta-model (quite easy ;) ).
+
+Also _Tamaya_ allows you to have multiple meta-models loaded in parallel, each one hereby
+is identified by a unique name. Nevertheless if no meta-model has been explicitly registered
+_Tamaya_ implicitly registers and loads a **simple** meta-model by default, which is as follows
+(first sources have lower priority):
+
+* **Default entries:** META-INF/cfg/default/**/*
+* **Explicit entries:** META-INF/cfg/config/**/*
+* **System Properties**
+* **Environment Properties**, mapped to _env.*_
+
+By default _.properties_, _.xml_ (properties) and _.ini_ file formats are supported.
+
+
 # Modules
 
 ## Integrations



Mime
View raw message